MediaWiki  1.28.0
HashConfig.php
Go to the documentation of this file.
1 <?php
28 class HashConfig implements Config, MutableConfig {
29 
35  private $settings;
36 
40  public static function newInstance() {
41  return new HashConfig;
42  }
43 
47  public function __construct( array $settings = [] ) {
48  $this->settings = $settings;
49  }
50 
54  public function get( $name ) {
55  if ( !$this->has( $name ) ) {
56  throw new ConfigException( __METHOD__ . ": undefined option: '$name'" );
57  }
58 
59  return $this->settings[$name];
60  }
61 
65  public function has( $name ) {
66  return array_key_exists( $name, $this->settings );
67  }
68 
72  public function set( $name, $value ) {
73  $this->settings[$name] = $value;
74  }
75 }
array
the array() calling protocol came about after MediaWiki 1.4rc1.
$value
$value
Definition: styleTest.css.php:45
ConfigException
Exceptions for config failures.
Definition: ConfigException.php:28
MutableConfig
Interface for mutable configuration instances.
Definition: MutableConfig.php:28
HashConfig\__construct
__construct(array $settings=[])
Definition: HashConfig.php:47
HashConfig\$settings
array $settings
Array of config settings.
Definition: HashConfig.php:35
settings
globals will be eliminated from MediaWiki replaced by an application object which would be passed to constructors Whether that would be an convenient solution remains to be but certainly PHP makes such object oriented programming models easier than they were in previous versions For the time being MediaWiki programmers will have to work in an environment with some global context At the time of globals were initialised on startup by MediaWiki of these were configuration settings
Definition: globals.txt:25
HashConfig\newInstance
static newInstance()
Definition: HashConfig.php:40
HashConfig\has
has($name)
Definition: HashConfig.php:65
php
injection txt This is an overview of how MediaWiki makes use of dependency injection The design described here grew from the discussion of RFC T384 The term dependency this means that anything an object needs to operate should be injected from the the object itself should only know narrow no concrete implementation of the logic it relies on The requirement to inject everything typically results in an architecture that based on two main types of and essentially stateless service objects that use other service objects to operate on the value objects As of the beginning MediaWiki is only starting to use the DI approach Much of the code still relies on global state or direct resulting in a highly cyclical dependency which acts as the top level factory for services in MediaWiki which can be used to gain access to default instances of various services MediaWikiServices however also allows new services to be defined and default services to be redefined Services are defined or redefined by providing a callback the instantiator that will return a new instance of the service When it will create an instance of MediaWikiServices and populate it with the services defined in the files listed by thereby bootstrapping the DI framework Per $wgServiceWiringFiles lists includes ServiceWiring php
Definition: injection.txt:35
HashConfig\set
set($name, $value)
Definition: HashConfig.php:72
HashConfig
A Config instance which stores all settings as a member variable.
Definition: HashConfig.php:28
$name
Allows to change the fields on the form that will be generated $name
Definition: hooks.txt:300