dff469a408
During development a lot of classes were placed in MediaWiki\Storage\. The precedent set would mean that every class relating to something stored in a database table, plus all related value classes and such, would go into that namespace. Let's put them into MediaWiki\Revision\ instead. Then future classes related to the 'page' table can go into MediaWiki\Page\, future classes related to the 'user' table can go into MediaWiki\User\, and so on. Note I didn't move DerivedPageDataUpdater, PageUpdateException, PageUpdater, or RevisionSlotsUpdate in this patch. If these are kept long-term, they probably belong in MediaWiki\Page\ or MediaWiki\Edit\ instead. Bug: T204158 Change-Id: I16bea8927566a3c73c07e4f4afb3537e05aa04a5
31 lines
763 B
PHP
31 lines
763 B
PHP
<?php
|
|
/**
|
|
* Created by PhpStorm.
|
|
* User: daki
|
|
* Date: 05.09.18
|
|
* Time: 16:08
|
|
*/
|
|
namespace MediaWiki\Revision;
|
|
|
|
use ParserOutput;
|
|
|
|
/**
|
|
* A lazy provider of ParserOutput objects for a revision's individual slots.
|
|
*
|
|
* @since 1.32
|
|
*/
|
|
interface SlotRenderingProvider {
|
|
|
|
/**
|
|
* @param string $role
|
|
* @param array $hints Hints given as an associative array. Known keys:
|
|
* - 'generate-html' => bool: Whether the caller is interested in output HTML (as opposed
|
|
* to just meta-data). Default is to generate HTML.
|
|
*
|
|
* @throws SuppressedDataException if the content is not accessible for the audience
|
|
* specified in the constructor.
|
|
* @return ParserOutput
|
|
*/
|
|
public function getSlotParserOutput( $role, array $hints = [] );
|
|
|
|
}
|