This is a follow-up to 🐛 Follow-up for #3361534: config validation errors can still occur for contrib modules, disrupting contrib Active and 📌 KernelTestBase::$strictConfigSchema = TRUE and BrowserTestBase::$strictConfigSchema = TRUE do not actually strictly validate Fixed , per #3364109-49: Configuration schema & required values: add test coverage for `nullable: true` validation support → .
Once 📌 Configuration schema & required values: add test coverage for `nullable: true` validation support Fixed lands, we'll have a reliable mechanism to detect which config schema types (i.e. simple config objects or config entity types) are fully validatable.
The changes 🐛 Follow-up for #3361534: config validation errors can still occur for contrib modules, disrupting contrib Active made should still be respected: we do NOT want config validation to be executed for every contrib module.
But we DO want run config validation for contrib modules when:
FullyValidatable constraintpublic function checkConfigSchema(TypedConfigManagerInterface $typed_config, $config_name, $config_data … has the FullyValidatable constraint as one of the values of $typed_config->getConstraints()N/A
TBD
TBD
TBD
TBD
TBD
TBD
Active
11.0 🔥
Last updated
It denotes an issue that prevents porting of a contributed project to the stable version of Drupal due to missing APIs, regressions, and so on.
All blockers appear to be in, at last, so this is unblocked.
Closed 📌 Follow-up for #3361534: config validation errors in contrib modules should not cause deprecation notices, unless they opt in Active since this is the last remaining issue in that plan! 👍