MediaWiki  master
Go to the documentation of this file.
1 <?php
23 namespace MediaWiki\Revision;
39  private $role;
45  private $layout = [
46  'display' => 'section', // use 'none' to suppress
47  'region' => 'center',
48  'placement' => 'append'
49  ];
54  private $contentModel;
64  public function __construct( $role, $contentModel, $layout = [] ) {
65  $this->role = $role;
66  $this->contentModel = $contentModel;
67  $this->layout = array_merge( $this->layout, $layout );
68  }
73  public function getRole() {
74  return $this->role;
75  }
97  public function getOutputLayoutHints() {
98  return $this->layout;
99  }
106  public function getNameMessageKey() {
107  return 'slot-name-' . $this->role;
108  }
121  public function getDefaultModel( LinkTarget $page ) {
122  return $this->contentModel;
123  }
140  public function isAllowedModel( $model, LinkTarget $page ) {
141  return ( $model === $this->contentModel );
142  }
155  public function supportsArticleCount() {
156  return false;
157  }
159 }
Apache License January AND DISTRIBUTION Definitions License shall mean the terms and conditions for use
Some information about database access in MediaWiki By Tim January Database layout For information about the MediaWiki database layout
Definition: database.txt:2
SlotRoleHandler instances are used to declare the existence and behavior of slot roles.
__construct( $role, $contentModel, $layout=[])
Created by PhpStorm.
The message key for the translation of the slot name.
Whether this slot should be considered when determining whether a page should be counted as an "artic...
getDefaultModel(LinkTarget $page)
Determines the content model to use per default for this slot on the given page.
Layout hints for use while laying out the combined output of all slots, typically by RevisionRenderer...
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
isAllowedModel( $model, LinkTarget $page)
Determines whether the given model can be used on this slot on the given page.