Change Details

For backwards compatibility, configuration values need to be available as global variables.

For backwards compatibility, configuration values need to be available as global variables. Care must be taken to correctly combine values loaded from settings files with values provided by DefaultSettings.php. This is particularly true for complex structures such as $wgGroupPermissions. The necessary merge strategies can be found in ExtensionRegistry. However, it is important to not that ExtensionRegistry is implemented to backfill defaults and avoids overriding existing values in the globals, while SettingsLoader would do the opposite: it would be overriding defaults present in the global variables. Further, it's important to avoid overriding globals that are not configuration, such as $wgHooks.

For backwards compatibility, configuration values need to be available as global variables. Care must be taken to correctly combine values loaded from settings files with values provided by DefaultSettings.php. This is particularly true for complex structures such as $wgGroupPermissions. The necessary merge strategies can be found in ExtensionRegistry. However, it is important to not that ExtensionRegistry is implemented to backfill defaults and avoids overriding existing values in the globals, while SettingsLoader would do the opposite: it would be overriding defaults present in the global variables. Further, it's important to avoid overriding globals that are not configuration, such as $wgHooks.