26 $this->testParser =
new Parser();
27 $this->testParser->Options( $this->testParserOptions );
28 $this->testParser->clearState();
30 $this->
title = Title::newFromText(
'Preload Test' );
36 unset( $this->testParser );
37 unset( $this->
title );
52 '<pre>monospaced</pre>',
53 '<pre>monospaced</pre>',
54 '<pre> in preloaded text must be unstripped (bug 27467)'
63 '<nowiki>[[Dummy title]]</nowiki>',
64 '<nowiki>[[Dummy title]]</nowiki>',
65 '<nowiki> in preloaded text must be unstripped (bug 27467)'
72 $this->testParser->getPreloadText(
75 $this->testParserOptions
Set options of the Parser.
static newFromUserAndLang(User $user, Language $lang)
Get a ParserOptions object from a given user and language.
Basic tests for Parser::getPreloadText.
testPreloadedPreIsUnstripped()
Parser::getPreloadText.
ParserOptions $testParserOptions
assertPreloaded( $expected, $text, $msg='')
testPreloadSimpleText()
Parser::getPreloadText.
testPreloadedNowikiIsUnstripped()
Parser::getPreloadText.
PHP Parser - Processes wiki markup (which uses a more user-friendly syntax, such as "[[link]]" for ma...
Represents a title within MediaWiki.
The User object encapsulates all of the user-specific settings (user_id, name, rights,...
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
when a variable name is used in a it is silently declared as a new local masking the global
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