MediaWiki REL1_32
ApiTestContext.php
Go to the documentation of this file.
1<?php
2
3class ApiTestContext extends RequestContext {
4
12 public function newTestContext( WebRequest $request, User $user = null ) {
13 $context = new DerivativeContext( $this );
14 $context->setRequest( $request );
15 if ( $user !== null ) {
16 $context->setUser( $user );
17 }
18
19 return $context;
20 }
21}
ApiTestContext\newTestContext
newTestContext(WebRequest $request, User $user=null)
Returns a DerivativeContext with the request variables in place.
Definition ApiTestContext.php:12
DerivativeContext
An IContextSource implementation which will inherit context from another source but allow individual ...
Definition DerivativeContext.php:30
RequestContext
Group all the pieces relevant to the context of a request into one instance.
Definition RequestContext.php:32
RequestContext\$request
WebRequest $request
Definition RequestContext.php:36
User
The User object encapsulates all of the user-specific settings (user_id, name, rights,...
Definition User.php:47
WebRequest
The WebRequest class encapsulates getting at data passed in the URL or via a POSTed form stripping il...
Definition WebRequest.php:41
$context
do that in ParserLimitReportFormat instead use this to modify the parameters of the image all existing parser cache entries will be invalid To avoid you ll need to handle that somehow(e.g. with the RejectParserCacheValue hook) because MediaWiki won 't do it for you. & $defaults also a ContextSource after deleting those rows but within the same transaction you ll probably need to make sure the header is varied on and they can depend only on the ResourceLoaderContext $context
Definition hooks.txt:2885
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