The functionality provided by $settings['config_overlay_priorities'] is currently untested.
Add a test that sets $settings['config_overlay_priorities']. In particular, it probably makes sense to test the "nested config split" functionality as described in the README.md:
If you have configuration splits that are shipped by modules that are themselves
split off by another configuration split, Config Split will not detect those
"nested" splits during the initial configuration import. To rectify this, set
the$settings['config_split_priorities']and
$settings['config_overlay_priorities']variables such that Config Overlay
always runs in between each level of nesting.For example:
$settings['config_split_priorities'] = [ 'shipped_in_module_aaa_splits_module_bbb' => 0, 'shipped_in_module_bbb_splits_module_ccc' => -20, 'shipped_in_module_ccc_splits_module_ddd' => -40, ]; $settings['config_overlay_priorities'] = [50, -10, -30, -50];
Active
2.0
Tests
Issue #3537019 by tstoeckler: Fix mismatch of settings name in code and...
Oops, that commit should have referenced 🐛 Mismatch of settings name in documentation and code Active instead of this issue.