Config inspection should wipe relevant caches to always get up-to-date results

+++ b/src/Commands/InspectorCommands.php
@@ -107,6 +118,12 @@ class InspectorCommands extends DrushCommands {
+    // Always inspect an up-to-date configuration schema.
+    $this->discoveryCache->deleteMultiple([
+      'typed_config_definitions',
+      'validation_constraint_plugins',
+    ]);

maybe drush can decorate the service with memoryCache and always skip this keys on get()

@andypost: I think its fine if we remove them from cache here, its a developer tool after all, so its more likely that you are tweaking the schema anyway, so it may be helpful in itself that it removes the schema cahes for the respective items?

Rerolled the patch against the current codebase. Does this only affect Drush?

#5: my thoughts exactly.

Does this only affect Drush?

Yes.

People using the Config Inspector UI would then indeed still get potentially stale information. But people may be using Config Inspector just to explore the values in their configuration. That's less likely in the Drush command.

So I figured that it would be potentially disruptive to do it also in the UI.

But … happy to change that. I have no strong opinion.

btw Drush using own kernel additionally to core's one, but I totally agree that current delete is nice workaround without extra complexity

For UI part we can add a description or even hook_help for route with description pointing to performance settings page where caches can be cleared

It can be just a description for the checkbox (show only errors) at the top of list

That sounds reasonable to me. Note that we could even show when the config schema was constructed & cached, based on the created column for the relevant row in the cache_discovery table! 🤓

Hm is cache clearing a concern on the UI because it would do too much clearing or be detrimental to performance of the tool? I would prefer consistency in how the two interfaces to the module work, otherwise you would get different results on the UI and in Drush, that could quickly get confusing.

Hm is cache clearing a concern on the UI because it would do too much clearing

This.

or be detrimental to performance of the tool

Not this. Config Inspector itself still does the same exact amount of work either way.

I would prefer consistency in how the two interfaces to the module work, otherwise you would get different results on the UI and in Drush, that could quickly get confusing.

WFM!

Done.

Retitle for the more general solution arrived at.

Thanks both!

Yay! 🥳

Automatically closed - issue fixed for 2 weeks with no activity.