[4.x] Cache rebuild is needed after composable schema configuration change

[drudoi]

Changes in composable schema configuration (extensions list) aren't seen in Explorer or Voyager till cache is rebuilded manually.

[larowlan]

Thats by design, calculating schema changes on every request would be expensive

If you are actively developing your schemas you can opt out of caching via your settings.local.php and services.local.yml

[drudoi]

I mean that specific tag should be assigned to the schema cache, and the tag should be invalidated on a server form submit.

P.S. By the way its really much easier to track issues in Drupal.org tracker, also I can provide a patch there - why is it disabled?