MediaWiki  master
ChangeTagsList.php
Go to the documentation of this file.
1 <?php
25 abstract class ChangeTagsList extends RevisionListBase {
26  function __construct( IContextSource $context, Title $title, array $ids ) {
27  parent::__construct( $context, $title );
28  $this->ids = $ids;
29  }
30 
41  public static function factory( $typeName, IContextSource $context,
42  Title $title, array $ids
43  ) {
44  switch ( $typeName ) {
45  case 'revision':
46  $className = ChangeTagsRevisionList::class;
47  break;
48  case 'logentry':
49  $className = ChangeTagsLogList::class;
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 }
wfGetDB
wfGetDB( $db, $groups=[], $wiki=false)
Get a Database object.
Definition: GlobalFunctions.php:2568
ContextSource\$context
IContextSource $context
Definition: ContextSource.php:33
DB_MASTER
const DB_MASTER
Definition: defines.php:26
ChangeTagsList\__construct
__construct(IContextSource $context, Title $title, array $ids)
Definition: ChangeTagsList.php:26
RevisionListBase
List for revision table items for a single page.
Definition: RevisionListBase.php:29
$params
$params
Definition: styleTest.css.php:41
ChangeTagsList
Generic list for change tagging.
Definition: ChangeTagsList.php:25
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.
class
you have access to all of the normal MediaWiki so you can get a DB use the etc For full docs on the Maintenance class
Definition: maintenance.txt:52
ChangeTagsList\updateChangeTagsOnAll
updateChangeTagsOnAll( $tagsToAdd, $tagsToRemove, $params, $reason, $user)
Add/remove change tags from all the items in the list.
ChangeTagsList\factory
static factory( $typeName, IContextSource $context, Title $title, array $ids)
Creates a ChangeTags*List of the requested type.
Definition: ChangeTagsList.php:41
$user
return true to allow those checks to and false if checking is done & $user
Definition: hooks.txt:1454
ChangeTagsList\reloadFromMaster
reloadFromMaster()
Reload the list data from the master DB.
Definition: ChangeTagsList.php:61