If a recipe's config has conflicts with active config, it throws a RecipePreExistingConfigException. This happens in \Drupal\Core\Recipe\ConfigConfigurator::__construct(), which is called the moment a recipe is even loaded from disk -- not even when it's applied.
If you need to inspect a recipe, without actually trying to apply it (in Project Browser, for example), this is way too aggressive and can lead to exceptions that seem to come out of nowhere.
We should have an explicit method on ConfigConfigurator which checks for conflicts with active config (it should just move the code that's already in __construct(); we don't need to implement any new logic). And we should call that method in two places:
Active
11.0 🔥
Well I think we should move all the active checks out of \Drupal\Core\Recipe\Recipe::parse() and into a validate method. This should make constructing recipe objects light enough for a general Recipe discovery mechanism and make things easier.
Ie… the calls to
validateExtensionIsAvailable
validateConfigActions
Should go into a validate() method. And the code in ConfigConfigurator::construct should also move into a validate function.