33 Title::newFromText( $dest ),
37 if ( $error ===
true ) {
38 $this->assertTrue(
$status->isGood() );
40 $this->assertTrue(
$status->hasMessage( $error ) );
47 [
'Test',
'Test2',
false,
true ],
51 [
'Test',
'Test2', strtotime(
'tomorrow' ),
true ],
52 [
'Test',
'Test',
false,
'mergehistory-fail-self-merge' ],
53 [
'Nonexistant',
'Test2',
false,
'mergehistory-fail-invalid-source' ],
54 [
'Test',
'Nonexistant',
false,
'mergehistory-fail-invalid-dest' ],
58 'This is obviously an invalid timestamp',
59 'mergehistory-fail-bad-timestamp'
71 $mh = $this->getMockBuilder(
'MergeHistory' )
72 ->setMethods( [
'getRevisionCount' ] )
73 ->setConstructorArgs( [
74 Title::newFromText(
'Test' ),
75 Title::newFromText(
'Test2' ),
78 $mh->expects( $this->once() )
79 ->method(
'getRevisionCount' )
80 ->will( $this->returnValue(
$limit + 1 ) );
83 $this->assertTrue(
$status->hasMessage(
'mergehistory-fail-toobig' ) );
84 $errors =
$status->getErrorsByType(
'error' );
86 $this->assertEquals(
$params[0], Message::numParam(
$limit ) );
95 Title::newFromText(
'Test' ),
96 Title::newFromText(
'Test2' )
100 $sysop = static::getTestSysop()->getUser();
101 $status = $mh->checkPermissions( $sysop,
'' );
102 $this->assertTrue(
$status->isOK() );
105 $notSysop = static::getTestUser()->getUser();
106 $status = $mh->checkPermissions( $notSysop,
'' );
107 $this->assertTrue(
$status->hasMessage(
'mergehistory-fail-permission' ) );
116 Title::newFromText(
'Merge1' ),
117 Title::newFromText(
'Merge2' )
120 $sysop = static::getTestSysop()->getUser();
121 $mh->merge( $sysop );
122 $this->assertEquals( $mh->getMergedRevisionCount(), 1 );
testGetMergedRevisionCount()
Test merged revision count MergeHistory::getMergedRevisionCount.
testCheckPermissions()
Test user permission checking MergeHistory::checkPermissions.
addDBDataOnce()
Make some pages to work with.
testIsValidMerge( $source, $dest, $timestamp, $error)
provideIsValidMerge MergeHistory::isValidMerge
static provideIsValidMerge()
testIsValidMergeRevisionLimit()
Test merge revision limit checking MergeHistory::isValidMerge.
Handles the backend logic of merging the histories of two pages.
const REVISION_LIMIT
@const int Maximum number of revisions that can be merged at once
this hook is for auditing only RecentChangesLinked and Watchlist RecentChangesLinked and Watchlist e g Watchlist removed from all revisions and log entries to which it was applied This gives extensions a chance to take it off their books as the deletion has already been partly carried out by this point or something similar the user will be unable to create the tag set $status
null means default in associative array with keys and values unescaped Should be merged with default with a value of false meaning to suppress the attribute in associative array with keys and values unescaped noclasses just before the function returns a value If you return true
this hook is for auditing only RecentChangesLinked and Watchlist RecentChangesLinked and Watchlist e g Watchlist removed from all revisions and log entries to which it was applied This gives extensions a chance to take it off their books as the deletion has already been partly carried out by this point or something similar the user will be unable to create the tag set and then return false from the hook function Ensure you consume the ChangeTagAfterDelete hook to carry out custom deletion actions as context called by AbstractContent::getParserOutput May be used to override the normal model specific rendering of page content as context as context the output can only depend on parameters provided to this hook not on global state indicating whether full HTML should be generated If generation of HTML may be but other information should still be present in the ParserOutput object to manipulate or replace but no entry for that model exists in $wgContentHandlers if desired whether it is OK to use $contentModel on $title Handler functions that modify $ok should generally return false to prevent further hooks from further modifying $ok inclusive $limit
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