- Issue created by @guiu.rocafort.ferrer
- πͺπΈSpain guiu.rocafort.ferrer Barcelona
I have been looking a little bit more on the topic, and i found a configuration attribute system.site.weight_select_max. This is set to 100 by default on site install ( see core/modules/system/config/install/system.site.yml ).
One option to make this data type validatable, would be having a callback to check the value of system.site.weight_select_max, and sets Range constraints for min: -VALUE, max: VALUE.
This does not seem to be respected by core.extensions.yml, which sets a value of 1000 for the install profile used.
I see three possible ways to deal with this:
- Change system.site.weight_select_max to have a value of 1000, then the core.extensions would be valid
- Change the site install behaviour, to add the install profile with a weight value of 100
- Keep the core.extension weights as type integer, and leave it as an exception.