MediaWiki  1.28.0
JavaScriptContentHandler.php
Go to the documentation of this file.
1 <?php
29 class JavaScriptContentHandler extends CodeContentHandler {
30 
34  public function __construct( $modelId = CONTENT_MODEL_JAVASCRIPT ) {
35  parent::__construct( $modelId, [ CONTENT_FORMAT_JAVASCRIPT ] );
36  }
37 
41  protected function getContentClass() {
42  return JavaScriptContent::class;
43  }
44 
45  public function supportsRedirects() {
46  return true;
47  }
48 
56  public function makeRedirectContent( Title $destination, $text = '' ) {
57  // The parameters are passed as a string so the / is not url-encoded by wfArrayToCgi
58  $url = $destination->getFullURL( 'action=raw&ctype=text/javascript', false, PROTO_RELATIVE );
59  $class = $this->getContentClass();
60  return new $class( '/* #REDIRECT */' . Xml::encodeJsCall( 'mw.loader.load', [ $url ] ) );
61  }
62 }
JavaScriptContentHandler
Content handler for JavaScript pages.
Definition: JavaScriptContentHandler.php:29
JavaScriptContentHandler\makeRedirectContent
makeRedirectContent(Title $destination, $text= '')
Create a redirect that is also valid JavaScript.
Definition: JavaScriptContentHandler.php:56
JavaScriptContentHandler\__construct
__construct($modelId=CONTENT_MODEL_JAVASCRIPT)
Definition: JavaScriptContentHandler.php:34
CodeContentHandler
Content handler for code content such as CSS, JavaScript, JSON, etc.
Definition: CodeContentHandler.php:29
PROTO_RELATIVE
const PROTO_RELATIVE
Definition: Defines.php:225
CONTENT_MODEL_JAVASCRIPT
CONTENT_MODEL_JAVASCRIPT
Uploads have to be specially set up to be secure.
Definition: DefaultSettings.php:974
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
class
you have access to all of the normal MediaWiki so you can get a DB use the etc For full docs on the Maintenance class
Definition: maintenance.txt:52
CONTENT_FORMAT_JAVASCRIPT
const CONTENT_FORMAT_JAVASCRIPT
Definition: Defines.php:256
Xml\encodeJsCall
static encodeJsCall($name, $args, $pretty=false)
Create a call to a JavaScript function.
Definition: Xml.php:682
Title\getFullURL
getFullURL($query= '', $query2=false, $proto=PROTO_RELATIVE)
Get a real URL referring to this title, with interwiki link and fragment.
Definition: Title.php:1672