MediaWiki  1.33.0
Go to the documentation of this file.
1 <?php
21  protected $targets = [ 'desktop', 'mobile' ];
28  $scripts = parent::getScript( $context );
30  return $scripts . Xml::encodeJsCall(
31  '', [
32  $this->getPygmentsLanguages()
33  ],
34  ResourceLoader::inDebugMode()
36  '', [
38  ],
39  ResourceLoader::inDebugMode()
41  '', [
43  ],
44  ResourceLoader::inDebugMode()
45  );
46  }
52  private function getPygmentsLanguages() {
53  return array_keys( require __DIR__ . '/../SyntaxHighlight.lexers.php' );
54  }
59  public function enableModuleContentVersion() {
60  return true;
61  }
66  public function supportsURLLoading() {
67  return false;
68  }
69 }
Object passed around to modules which contains information about the state of a specific loader reque...
Definition: ResourceLoaderContext.php:32
do that in ParserLimitReportFormat instead use this to modify the parameters of the image all existing parser cache entries will be invalid To avoid you ll need to handle that somehow(e.g. with the RejectParserCacheValue hook) because MediaWiki won 't do it for you. & $defaults also a ContextSource after deleting those rows but within the same transaction you ll probably need to make sure the header is varied on and they can depend only on the ResourceLoaderContext $context
Definition: hooks.txt:2636
This program is free software; you can redistribute it and/or modify it under the terms of the GNU Ge...
Definition: ResourceLoaderSyntaxHighlightVisualEditorModule.php:19
getScript(ResourceLoaderContext $context)
Definition: ResourceLoaderSyntaxHighlightVisualEditorModule.php:27
Get a full list of available languages.
Definition: ResourceLoaderSyntaxHighlightVisualEditorModule.php:52
Definition: ResourceLoaderSyntaxHighlightVisualEditorModule.php:59
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
ResourceLoader module based on local JavaScript/CSS files.
Definition: ResourceLoaderFileModule.php:28
static encodeJsCall( $name, $args, $pretty=false)
Create a call to a JavaScript function.
Definition: Xml.php:677
static getGeSHiToPygmentsMap()
Definition: SyntaxHighlightGeSHiCompat.php:110
static getPygmentsToAceMap()
Definition: SyntaxHighlightAce.php:160
Definition: ResourceLoaderSyntaxHighlightVisualEditorModule.php:21
array $scripts
List of paths to JavaScript files to always include.
Definition: ResourceLoaderFileModule.php:46
Definition: ResourceLoaderSyntaxHighlightVisualEditorModule.php:66