MediaWiki  1.28.1
Go to the documentation of this file.
1 <?php
23  public function testBug41337() {
25  // Set a low limit
26  $this->setMwGlobals( 'wgMaxSigChars', 2 );
28  $user = $this->getMock( 'User' );
29  $user->expects( $this->any() )
30  ->method( 'isAnon' )
31  ->will( $this->returnValue( false ) );
33  # Yeah foreach requires an array, not NULL =(
34  $user->expects( $this->any() )
35  ->method( 'getEffectiveGroups' )
36  ->will( $this->returnValue( [] ) );
38  # The mocked user has a long nickname
39  $user->expects( $this->any() )
40  ->method( 'getOption' )
41  ->will( $this->returnValueMap( [
42  [ 'nickname', null, false, 'superlongnickname' ],
43  ]
44  ) );
46  # Forge a request to call the special page
47  $context = new RequestContext();
48  $context->setRequest( new FauxRequest() );
49  $context->setUser( $user );
50  $context->setTitle( Title::newFromText( 'Test' ) );
52  # Do the call, should not spurt a fatal error.
54  $special->setContext( $context );
55  $this->assertNull( $special->execute( [] ) );
56  }
58 }
this hook is for auditing only RecentChangesLinked and Watchlist $special
Definition: hooks.txt:1007
Group all the pieces relevant to the context of a request into one instance.
Definition: load.php:50
Make sure a nickname which is longer than $wgMaxSigChars is not throwing a fatal error.
Test class for SpecialPreferences class.
static newFromText($text, $defaultNamespace=NS_MAIN)
Create a new Title from text, such as what one would find in a link.
Definition: Title.php:262
A special page that allows users to change their preferences.
please add to it if you re going to add events to the MediaWiki code where normally authentication against an external auth plugin would be creating a local account $user
Definition: hooks.txt:242
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
setMwGlobals($pairs, $value=null)