- 🇺🇸United States xjm
This was already added to the 10.1.0 release notes draft.
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
This is now helping us at #3361534-15: KernelTestBase::$strictConfigSchema = TRUE does not actually strictly validate → ! 🥳
🌱 [META] Untie config validation from form validation — enables validatable Recipes, decoupled admin UIs … Active proposed to start using validation constraints for validating all config entities.
One of the generic aspects of config entities is this:
config_entity:
type: mapping
mapping:
…
dependencies:
type: config_dependencies
label: 'Dependencies'
…
which is defined as:
config_dependencies_base:
type: mapping
mapping:
config:
type: sequence
label: 'Configuration entity dependencies'
sequence:
type: string
content:
type: sequence
label: 'Content entity dependencies'
sequence:
type: string
module:
type: sequence
label: 'Module dependencies'
sequence:
type: string
theme:
type: sequence
label: 'Theme dependencies'
sequence:
type: string
config_dependencies:
type: config_dependencies_base
label: 'Configuration dependencies'
mapping:
enforced:
type: config_dependencies_base
label: 'Enforced configuration dependencies'
If validation constraints are written for this, then … all config entities will already have some validation! Plus, it will help make validation "complete" for config entity types whose specific validation constraints are already written (first in line: 📌 [PP-1] Convert field_storage_config and field_config's form validation logic to validation constraints Postponed ).
dependencies.config dependencies actually exist
dependencies.content, dependencies.module and dependencies.theme
type: string for every case where the value is not just any string but a particular kind of string
Bonus (because not sure if actually feasible): if a config entity type is known to depend on another config entity (for example: a field_config entity always needs a field_storage_config entity — at minimum), but it doesn't specify such a dependency, fail validation in that case too.
Note: dependencies.enforced.* should then "just work"! 😊
TBD
None.
None.
None.
Config dependencies now have validation constraints. → These are not actively used by Drupal core, but will take effect as support is added for validating config entities at the data layer.
Fixed
10.1 ✨
Last updated
Enhances developer experience.
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.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This was already added to the 10.1.0 release notes draft.
This is now helping us at #3361534-15: KernelTestBase::$strictConfigSchema = TRUE does not actually strictly validate → ! 🥳