MediaWiki  1.29.1
Go to the documentation of this file.
1 <?php
5  public function __construct( $dataModel ) {
6  parent::__construct( $dataModel, [ "testing" ] );
7  }
17  public function serializeContent( Content $content, $format = null ) {
18  return $content->serialize();
19  }
29  public function unserializeContent( $blob, $format = null ) {
30  $d = unserialize( $blob );
32  return new DummyContentForTesting( $d );
33  }
38  public function makeEmptyContent() {
39  return new DummyContentForTesting( '' );
40  }
41 }
A content handler knows how do deal with a specific type of content on a wiki page.
Definition: ContentHandler.php:49
unserialize( $serialized)
Definition: ApiMessage.php:185
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
Definition: testCompression.php:63
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 and Watchlist you will want to construct new ChangesListBooleanFilter or ChangesListStringOptionsFilter objects When constructing you specify which group they belong to You can reuse existing or create your you must register them with $special registerFilterGroup 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 $content
Definition: hooks.txt:1049
Creates an empty Content object of the type supported by this ContentHandler.
Definition: DummyContentHandlerForTesting.php:38
serializeContent(Content $content, $format=null)
Definition: DummyContentHandlerForTesting.php:17
Definition: DummyContentForTesting.php:3
Base interface for content objects.
Definition: Content.php:34
__construct( $dataModel)
Definition: DummyContentHandlerForTesting.php:5
unserializeContent( $blob, $format=null)
Definition: DummyContentHandlerForTesting.php:29
Definition: DummyContentHandlerForTesting.php:3