MediaWiki  1.30.0
ArticleTablesTest.php
Go to the documentation of this file.
1 <?php
2 
16  $title = Title::newFromText( 'T16404' );
17  $page = WikiPage::factory( $title );
18  $user = new User();
19  $user->mRights = [ 'createpage', 'edit', 'purge' ];
20  $this->setContentLang( 'es' );
21  $this->setUserLang( 'fr' );
22 
23  $page->doEditContent(
24  new WikitextContent( '{{:{{int:history}}}}' ),
25  'Test code for T16404',
26  0,
27  false,
28  $user
29  );
30  $templates1 = $title->getTemplateLinksFrom();
31 
32  $this->setUserLang( 'de' );
33  $page = WikiPage::factory( $title ); // In order to force the re-rendering of the same wikitext
34 
35  // We need an edit, a purge is not enough to regenerate the tables
36  $page->doEditContent(
37  new WikitextContent( '{{:{{int:history}}}}' ),
38  'Test code for T16404',
40  false,
41  $user
42  );
43  $templates2 = $title->getTemplateLinksFrom();
44 
49  $this->assertEquals( $templates1, $templates2 );
50  $this->assertEquals( $templates1[0]->getFullText(), 'Historial' );
51  }
52 }
$user
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 account $user
Definition: hooks.txt:244
Title\newFromText
static newFromText( $text, $defaultNamespace=NS_MAIN)
Create a new Title from text, such as what one would find in a link.
Definition: Title.php:268
User
User
Definition: All_system_messages.txt:425
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
$title
namespace and then decline to actually register it file or subcat img or subcat $title
Definition: hooks.txt:932
WikiPage\factory
static factory(Title $title)
Create a WikiPage object of the appropriate class for the given title.
Definition: WikiPage.php:121
MediaWikiTestCase\setUserLang
setUserLang( $lang)
Definition: MediaWikiTestCase.php:877
WikitextContent
Content object for wiki text pages.
Definition: WikitextContent.php:33
ArticleTablesTest\testTemplatelinksUsesContentLanguage
testTemplatelinksUsesContentLanguage()
Make sure that T16404 doesn't strike again.
Definition: ArticleTablesTest.php:15
MediaWikiTestCase\setContentLang
setContentLang( $lang)
Definition: MediaWikiTestCase.php:886
EDIT_UPDATE
const EDIT_UPDATE
Definition: Defines.php:154
ArticleTablesTest
Database.
Definition: ArticleTablesTest.php:6
MediaWikiLangTestCase
Base class that store and restore the Language objects.
Definition: MediaWikiLangTestCase.php:6