MediaWiki REL1_28
MediaWikiLangTestCase.php
Go to the documentation of this file.
1<?php
2
6abstract class MediaWikiLangTestCase extends MediaWikiTestCase {
7 protected function setUp() {
8 global $wgLanguageCode, $wgContLang;
9
10 if ( $wgLanguageCode != $wgContLang->getCode() ) {
11 throw new MWException( "Error in MediaWikiLangTestCase::setUp(): " .
12 "\$wgLanguageCode ('$wgLanguageCode') is different from " .
13 "\$wgContLang->getCode() (" . $wgContLang->getCode() . ")" );
14 }
15
16 parent::setUp();
17
18 $this->setUserLang( 'en' );
19 // For mainpage to be 'Main Page'
20 $this->setContentLang( 'en' );
21
22 MessageCache::singleton()->disable();
23 }
24}
$wgLanguageCode
$wgLanguageCode
Site language code.
Definition DefaultSettings.php:2828
MWException
MediaWiki exception.
Definition MWException.php:26
MediaWikiLangTestCase
Base class that store and restore the Language objects.
Definition MediaWikiLangTestCase.php:6
MessageCache\singleton
static singleton()
Get the signleton instance of this class.
Definition MessageCache.php:102
$wgContLang
this class mediates it Skin Encapsulates a look and feel for the wiki All of the functions that render HTML and make choices about how to render it are here and are called from various other places when and is meant to be subclassed with other skins that may override some of its functions The User object contains a reference to a and so rather than having a global skin object we just rely on the global User and get the skin with $wgUser and also has some character encoding functions and other locale stuff The current user interface language is instantiated as and the local content language as $wgContLang
Definition design.txt:57
global
when a variable name is used in a it is silently declared as a new local masking the global
Definition design.txt:95
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:37