A big set of fails in
field.*.storage_settings schemas (for fields that don't have storage settings). Unfortunately it is not possible to provide such a wildcard fallback pattern with an empty sequence because wildcards would only be allowed at the end. So the only way to fix those issues without changing the naming of these field schema components is to copy paste empty settings sequences to all the schemas that need them. That sounds like a waste of time and wrong DX. Also the dynamic portion in the middle is not consistent with other dynamic typing in config schemas.
1. We need to rework the internal schema names related to fields to be consistent with other names with dynamic components and to be able to provide a wildcard fallback.
2. This allows the introduction of an empty sequence fallback for
field.storage_settings.*. If the fields that fall back to this schema do have settings, that will fail on any schema testing (including ). Those (test) fields that actually don't have settings don't need to define this schema. (I kept the schema definitions of empty sequence storage settings for some core fields because they also relabel the settings key to be more specific).
User interface changes
The schema changes only concern keys used internally in schemas. Modules defining fields / field schemas are affected but no configuration keys need to change.
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 81,717 pass(es). View
|#53||2370305-field-type-schema-53.patch||30.15 KB||Gábor Hojtsy|
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] Unable to apply patch 2370305-field-type-schema-53.patch. Unable to apply patch. See the log in the details link for more information. View
|#51||2370305-field-type-schema-48.patch||30.27 KB||Gábor Hojtsy|
FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] Unable to apply patch 2370305-field-type-schema-48_0.patch. Unable to apply patch. See the log in the details link for more information. View
|#49||interdiff.txt||7.18 KB||Gábor Hojtsy|