Follow-up to #2361539: Config export key order is not predictable for sequences, add orderby property to config schema →
As shown in #2350821: Sort views displays by display name → and #2350537: Enforce order of display of components in config export → shows that even though #2256679: Use config schema to determine which config entity properties to export regardless of whether they are public or protected → made use of config schema to export the top level keys, for lower levels we still rely on the data provided as-is. That means that if keys are reordered for some reason, there will be unnecessary diffs. We should sorting maps in the same way order that the mapping is defined in the schema.
In the absence of a solution in core, various approaches have sprung up in contrib aimed at normalizing config for purposes of comparison or merging. These include:
NormalizedStorage in
Config Layers →
.ConfigItemNormalizer and NormalizedReadOnlyStorage in Configuration Normalizer.ConfigDiffer::normalize() in
Configuration Update Manager →
.SortedConfigFilter in
Sorted Configurations →
(sandbox module).ConfigSorter in
Config Split →
.
Use the order defined in a config schema data types mapping to sort the result configuration array. This makes the entire system work the same was as #2256679: Use config schema to determine which config entity properties to export regardless of whether they are public or protected → .
Agree. Do it.
None.
None?
Some configuration re-ordered.
Config is sorted by the order defined in its schema. You should always re-export configuration and commit it to version control after running updates. See the change record → for more recommendations.
Fixed
9.3
Last updated
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I think something related still happens to us in our projects.
After a Drupal or module update, it happens very often that when I do a cex I see a lot of changes. But they are not changes that we have actually made. For example, changes of the position in the yml.
Example screenshot: