It is possible to create a configuration object for each extension or skin during registration from their settings. It will be helpful for extensions to have an automatically generated config and that way, we'll be able to deprecate GlobalVarConfig.
|mediawiki/core||master||+476 -149||Create config for each extension/skin during registration|
|Open||None||T11968 Reduce use of global and public variables|
|Open||None||T156646 Make a config object for each extension/skin, deprecate GlobalVarConfig and RequestContext::getConfig()|
|Declined||Cenarium||T156877 Create a config object for each extension/skin during registration|
- Mentioned In
- T156646: Make a config object for each extension/skin, deprecate GlobalVarConfig and RequestContext::getConfig()
T142663: ExtensionRegistry does not allow complete override of config variables e.g. flat arrays
- Mentioned Here
- T249564: Determine purpose of GlobalVarConfig-backend entries in ConfigFactory (via wgConfigRegistry)
T155154: Don't require extensions to set ConfigRegistry
They both would make it unnecessary for extensions to set ConfigRegistry, but T155154 suggests a GlobalVarConfig object while this one suggests a new LocalConfig object (see https://gerrit.wikimedia.org/r/#/c/335383/5/includes/config/LocalConfig.php) that would be based only on the extension's own settings and handle merging with local settings. Eventually, this aims to deprecate GlobalVarConfig, and do the same thing for core (achieving a separation of configs and the removal of configuration globals).