MediaWiki  1.30.0
WatchedItemQueryServiceExtension.php
Go to the documentation of this file.
1 <?php
2 
5 
17 
35  array &$tables, array &$fields, array &$conds, array &$dbOptions, array &$joinConds
36  );
37 
54  array &$items, $res, &$startFrom
55  );
56 
57 }
$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
WatchedItemQueryServiceExtension\modifyWatchedItemsWithRCInfo
modifyWatchedItemsWithRCInfo(User $user, array $options, IDatabase $db, array &$items, $res, &$startFrom)
Modify the results from WatchedItemQueryService::getWatchedItemsWithRecentChangeInfo() before they're...
WatchedItemQueryServiceExtension
Definition: WatchedItemQueryServiceExtension.php:16
$tables
this hook is for auditing only RecentChangesLinked and Watchlist RecentChangesLinked and Watchlist Do not use this to implement individual filters if they are compatible with the ChangesListFilter and ChangesListFilterGroup structure use sub classes of those in conjunction with the ChangesListSpecialPageStructuredFilters hook This hook can be used to implement filters that do not implement that or custom behavior that is not an individual filter e g Watchlist & $tables
Definition: hooks.txt:988
use
as see the revision history and available at free of to any person obtaining a copy of this software and associated documentation to deal in the Software without including without limitation the rights to use
Definition: MIT-LICENSE.txt:10
$res
$res
Definition: database.txt:21
Wikimedia\Rdbms\ResultWrapper
Result wrapper for grabbing data queried from an IDatabase object.
Definition: ResultWrapper.php:24
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
Wikimedia\Rdbms\IDatabase
Basic database interface for live and lazy-loaded relation database handles.
Definition: IDatabase.php:40
WatchedItemQueryServiceExtension\modifyWatchedItemsWithRCInfoQuery
modifyWatchedItemsWithRCInfoQuery(User $user, array $options, IDatabase $db, array &$tables, array &$fields, array &$conds, array &$dbOptions, array &$joinConds)
Modify the WatchedItemQueryService::getWatchedItemsWithRecentChangeInfo() query before it's made.
$options
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 & $options
Definition: hooks.txt:1965
User
The User object encapsulates all of the user-specific settings (user_id, name, rights,...
Definition: User.php:51
array
the array() calling protocol came about after MediaWiki 1.4rc1.