MediaWiki  1.30.0
view.php
Go to the documentation of this file.
1 <?php
24 require_once __DIR__ . '/Maintenance.php';
25 
31 class ViewCLI extends Maintenance {
32  public function __construct() {
33  parent::__construct();
34  $this->addDescription( 'Show article contents on the command line' );
35  $this->addArg( 'title', 'Title of article to view' );
36  }
37 
38  public function execute() {
39  $title = Title::newFromText( $this->getArg() );
40  if ( !$title ) {
41  $this->error( "Invalid title", true );
42  }
43 
44  $page = WikiPage::factory( $title );
45 
46  $content = $page->getContent( Revision::RAW );
47  if ( !$content ) {
48  $this->error( "Page has no content", true );
49  }
50  if ( !$content instanceof TextContent ) {
51  $this->error( "Non-text content models not supported", true );
52  }
53 
54  $this->output( $content->getNativeData() );
55  }
56 }
57 
58 $maintClass = "ViewCLI";
59 require_once RUN_MAINTENANCE_IF_MAIN;
Title\newFromText
static newFromText( $text, $defaultNamespace=NS_MAIN)
Create a new Title from text, such as what one would find in a link.
Definition: Title.php:268
ViewCLI
Maintenance script to show page contents.
Definition: view.php:31
Maintenance\addDescription
addDescription( $text)
Set the description text.
Definition: Maintenance.php:287
RUN_MAINTENANCE_IF_MAIN
require_once RUN_MAINTENANCE_IF_MAIN
Definition: maintenance.txt:50
ViewCLI\execute
execute()
Do the actual work.
Definition: view.php:38
Maintenance
Abstract maintenance class for quickly writing and churning out maintenance scripts with minimal effo...
Definition: maintenance.txt:39
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
$title
namespace and then decline to actually register it file or subcat img or subcat $title
Definition: hooks.txt:932
WikiPage\factory
static factory(Title $title)
Create a WikiPage object of the appropriate class for the given title.
Definition: WikiPage.php:121
ViewCLI\__construct
__construct()
Default constructor.
Definition: view.php:32
Revision\RAW
const RAW
Definition: Revision.php:100
TextContent
Content object implementation for representing flat text.
Definition: TextContent.php:35
Maintenance\addArg
addArg( $arg, $description, $required=true)
Add some args that are needed.
Definition: Maintenance.php:267
Maintenance\error
error( $err, $die=0)
Throw an error to the user.
Definition: Maintenance.php:392
Maintenance\output
output( $out, $channel=null)
Throw some output to the user.
Definition: Maintenance.php:373
Maintenance\getArg
getArg( $argId=0, $default=null)
Get an argument.
Definition: Maintenance.php:306
$maintClass
$maintClass
Definition: view.php:58