Voting starts in March for the Drupal Association Board election.
Thepatch introduced a way to add langcode automatically to top level configuration names. @alexpott expressed concern that that adds an implicit assumption about configuration schema that is not explicitly in the type, and we should introduce explicit configuration language codes instead.
1. Add a config_object base type. This means that for a configuration name, developers would either define it using config_object or config_entity. This makes it REALLY easy to spot definitions for high level config in schemas.
2. Use the config_object base type for top level configuration (which are not config entities). Remove explicit langcodes from the ones now extending config_object.
3. Fix language.mappings which used a top level sequence type (and therefore incompatible with adding a top level langcode).
4. Remove breakpoint schemas which are not even for configuration, they are for plugin data (not stored within configuration).
5. Fix tests.
User interface changes
Configuration objects should now extend from
Beta phase evaluation
|Issue category||Bug because config files cannot be parsed by their schema alone, unless the langcode key is explicitly defined on them.|
|Issue priority||Major because the extent of changes required.|
|Disruption||Disruption in how configuration schemas need to be defined.|
|#30||interdiff.txt||2.23 KB||Gábor Hojtsy|
|#30||2459971-30.patch||40.69 KB||Gábor Hojtsy|
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 90,449 pass(es). View
|#27||interdiff.txt||18 KB||Gábor Hojtsy|
|#27||2459971-27.patch||38.72 KB||Gábor Hojtsy|
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] 90,570 pass(es), 5 fail(s), and 0 exception(s). View
|#26||2459971-26.patch||21.21 KB||Gábor Hojtsy|
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 90,582 pass(es). View