master/php/MutableContext_8php_source.html

 <?php

 interface MutableContext {

     public function setConfig( Config $c );


     public function setRequest( WebRequest $r );


     public function setTitle( Title $t );


     public function setWikiPage( WikiPage $p );


     public function setOutput( OutputPage $o );


     public function setUser( User $u );


     public function setLanguage( $l );


     public function setSkin( Skin $s );


 }

MutableContext\setSkin
setSkin(Skin $s)
Set the Skin object.

Skin
The main skin class which provides methods and properties for all other skins.
Definition: Skin.php:34

MutableContext\setTitle
setTitle(Title $t)
Set the Title object.

WebRequest
The WebRequest class encapsulates getting at data passed in the URL or via a POSTed form stripping il...
Definition: WebRequest.php:37

MutableContext
Definition: MutableContext.php:25

$s
$s
Definition: mergeMessageFileList.php:198

Title
Represents a title within MediaWiki.
Definition: Title.php:36

$t
$t
Definition: testCompression.php:67

MutableContext\setConfig
setConfig(Config $c)
Set the Config object.

User
The User object encapsulates all of the user-specific settings (user_id, name, rights, email address, options, last login time).
Definition: User.php:47

Config
Interface for configuration instances.
Definition: Config.php:28

MutableContext\setWikiPage
setWikiPage(WikiPage $p)
Set the WikiPage object.

MutableContext\setLanguage
setLanguage($l)
Set the Language object.

OutputPage
This class should be covered by a general architecture document which does not exist as of January 20...
Definition: OutputPage.php:43

WikiPage
Class representing a MediaWiki article and history.
Definition: WikiPage.php:31

MutableContext\setUser
setUser(User $u)
Set the User object.

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

MutableContext\setRequest
setRequest(WebRequest $r)
Set the WebRequest object.

MutableContext\setOutput
setOutput(OutputPage $o)
Set the OutputPage object.