wiki.techinc.nl/tests/phpunit/unit/includes/Settings/Source
Aryeh Gregor b72b9a8c43 Move dynamic defaults into MainConfigSchema
The goal is to keep the actual default values for settings in the same
place as the setting is declared, and applied using the regular means
for loading the settings -- not in a separate piece of code that needs
to be loaded through some entirely different mechanism.

SetupDynamicConfig.php now contains a few categories of things:

* Post-processing of configuration settings, where already-set settings
  are altered. This could be moved to MainConfigSchema too as a separate
  set of methods.
* Processing of old aliases of settings (blacklist, slave) that are not
  registered as settings anymore and therefore are not available to
  MainConfigSchema. This could perhaps be moved to LocalSettings
  processing somehow?
* Setting $wgUseEnotif, which is also not registered as a setting.
  Easiest would be just to declare it as a setting and have it set
  unconditionally.
* Setting the actual timezone to $wgLocaltimezone. This is not related
  to configuration and should just be in Setup.php.

Bug: T305093
Change-Id: Ia5c23b52dbbfcb3d07ffcf5d3b7f2d7befba2a26
2022-07-07 09:55:48 +10:00
..
fixtures Support etcd as a source for SettingsLoader 2022-06-21 17:17:32 +00:00
Format
ArraySourceTest.php
EtcdSourceTest.php Support etcd as a source for SettingsLoader 2022-06-21 17:17:32 +00:00
FileSourceTest.php tests: Rename fixtures/bad.json 2022-04-20 15:17:36 +01:00
JsonSchemaTraitTest.php Add support for nested property schemas in MainConfigSchema. 2022-06-29 16:34:43 +10:00
PhpSettingsSourceTest.php Follow up on I91cd04d14f0ff86125fc8870984dab045c2098b5 2021-12-17 19:14:35 +01:00
ReflectionSchemaSourceTest.php Move dynamic defaults into MainConfigSchema 2022-07-07 09:55:48 +10:00