MediaWiki  1.30.0
ChangeTagsList.php
Go to the documentation of this file.
1 <?php
25 abstract class ChangeTagsList extends RevisionListBase {
27  parent::__construct( $context, $title );
28  $this->ids = $ids;
29  }
30 
41  public static function factory( $typeName, IContextSource $context,
43  ) {
44  switch ( $typeName ) {
45  case 'revision':
46  $className = 'ChangeTagsRevisionList';
47  break;
48  case 'logentry':
49  $className = 'ChangeTagsLogList';
50  break;
51  default:
52  throw new Exception( "Class $typeName requested, but does not exist" );
53  }
54 
55  return new $className( $context, $title, $ids );
56  }
57 
61  function reloadFromMaster() {
62  $dbw = wfGetDB( DB_MASTER );
63  $this->res = $this->doQuery( $dbw );
64  }
65 
76  abstract function updateChangeTagsOnAll( $tagsToAdd, $tagsToRemove, $params,
77  $reason, $user );
78 }
ChangeTagsList
Generic list for change tagging.
Definition: ChangeTagsList.php:25
ContextSource\$context
IContextSource $context
Definition: ContextSource.php:34
$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
ChangeTagsList\updateChangeTagsOnAll
updateChangeTagsOnAll( $tagsToAdd, $tagsToRemove, $params, $reason, $user)
Add/remove change tags from all the items in the list.
RevisionListBase
List for revision table items for a single page.
Definition: RevisionList.php:30
$params
$params
Definition: styleTest.css.php:40
ChangeTagsList\reloadFromMaster
reloadFromMaster()
Reload the list data from the master DB.
Definition: ChangeTagsList.php:61
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
RevisionListBase\doQuery
doQuery( $db)
Do the DB query to iterate through the objects.
wfGetDB
wfGetDB( $db, $groups=[], $wiki=false)
Get a Database object.
Definition: GlobalFunctions.php:2856
RevisionListBase\$title
Title $title
Definition: RevisionList.php:32
DB_MASTER
const DB_MASTER
Definition: defines.php:26
RevisionListBase\$ids
array $ids
Definition: RevisionList.php:35
IContextSource
Interface for objects which can provide a MediaWiki context on request.
Definition: IContextSource.php:55
Title
Represents a title within MediaWiki.
Definition: Title.php:39
ChangeTagsList\factory
static factory( $typeName, IContextSource $context, Title $title, array $ids)
Creates a ChangeTags*List of the requested type.
Definition: ChangeTagsList.php:41
ChangeTagsList\__construct
__construct(IContextSource $context, Title $title, array $ids)
Definition: ChangeTagsList.php:26
array
the array() calling protocol came about after MediaWiki 1.4rc1.