A. The property AKA uknown AKA default type needs to be clarified.
B. While the above made it appear Property is the type to use to mark items as 'whatever type' that is not true.
A1. core.data_types.schema.yml defines it as both 'undefined' and 'default'. The 'default' type is not used. Should be removed.
A2. ConfigSchemaTestBase::checkValue() refers to Property in inappropriate contexts, inside checking for values implementing PrimitiveInterface while Property does not do that. That reference should be removed.
B1. An explicit 'ignore' type should be introduced to identify when something was explicitly defined as having no discernible type. This is so far only needed for migrations and we are not encouraging people to use that at all in other scenarios although we'll not be able to stop them. It should be explained this is done because migrations are optimized to be written by hand unlike most configuration entities which are saved by code thus have a more rigid schema.
User interface changes
- Less redundancy/confusion in the usage of the property type.
- New 'ignore' type.
|#44||interdiff.txt||3.29 KB||Gábor Hojtsy|
|#44||2264179.44.patch||19.05 KB||Gábor Hojtsy|
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 71,693 pass(es). View
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 71,606 pass(es). View
|#35||interdiff.txt||1.38 KB||Gábor Hojtsy|
|#35||2264179-add-property-35.patch||18.34 KB||Gábor Hojtsy|
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 71,490 pass(es). View