Whilst discussingwith @catch, @effulgentsia, @webchick and @xjm since it was tagged with "revisit before release candidate", we decided that we need to ensure that the configuration shipped with core in yml files matches the configuration in the active store after it is installed. This is important since incorrect default configuration can cause unexpected bugs and confusion for developers.
Revisit all configuration and make sure auto generated with latest config/plugin/schema changes.
This was done before whilst creating many of the configuration schema. For example, https://gist.github.com/alexpott/f0650fbb7954df8497e4and the beginnings of a script to do this is available at
Discuss what we should do about config provided by test modules Re-export the files in the installation profile Adapt the config_refresh module to also export optional default config, see Use the former to also export all optional config in core/modules core/profiles/(standard|minimal)
- Currently the patch contains mainly out of two parts: a) reordering of existing config b) adding defaults values back. In order to make it easier to review the first patch we could do the following: Write a script which looks at all the config files in HEAD and sorts it strictly alphabetically. We then could do the same with the files after this patch.
When we then compare these two sets of files we have excluded the orderings and the only remaining bits are additions/removals.
User interface changes
Data model changes
Should be none
PASSED: [[SimpleTest]]: [PHP 5.5 MySQL] 113,864 pass(es). View
FAILED: [[SimpleTest]]: [PHP 5.5 MySQL] 110,266 pass(es), 64 fail(s), and 22 exception(s). View
FAILED: [[SimpleTest]]: [PHP 5.5 MySQL] Unable to apply patch 2567183-88.patch. Unable to apply patch. See the log in the details link for more information. View