MediaWiki  REL1_31
Go to the documentation of this file.
1 <?php
26 class TidySupport {
27  private $enabled;
28  private $config;
34  public function __construct( $useConfiguration = false ) {
38  $this->enabled = true;
39  if ( $useConfiguration ) {
40  if ( $wgTidyConfig !== null ) {
41  $this->config = $wgTidyConfig;
42  } elseif ( $wgUseTidy ) {
43  $this->config = [
44  'tidyConfigFile' => $wgTidyConf,
45  'debugComment' => false,
46  'tidyBin' => $wgTidyBin,
47  'tidyCommandLine' => $wgTidyOpts
48  ];
49  if ( $wgTidyInternal ) {
50  $this->config['driver'] = wfIsHHVM() ? 'RaggettInternalHHVM' : 'RaggettInternalPHP';
51  } else {
52  $this->config['driver'] = 'RaggettExternal';
53  }
54  } else {
55  $this->enabled = false;
56  }
57  } else {
58  $this->config = [ 'driver' => 'RemexHtml' ];
59  }
60  if ( !$this->enabled ) {
61  $this->config = [ 'driver' => 'disabled' ];
62  }
63  }
70  public function isEnabled() {
71  return $this->enabled;
72  }
74  public function getConfig() {
75  return $this->config;
76  }
77 }
Definition: TidySupport.php:74
__construct( $useConfiguration=false)
Determine if there is a usable tidy.
Definition: TidySupport.php:34
Definition: TidySupport.php:27
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:37
Initialize and detect the tidy support.
Definition: TidySupport.php:26
Definition: TidySupport.php:28
when a variable name is used in a it is silently declared as a new masking the global
Definition: design.txt:95
The path to the tidy config file.
Definition: DefaultSettings.php:4315
Set this to true to use the tidy extension.
Definition: DefaultSettings.php:4327
Set this to true to use the deprecated tidy configuration parameters.
Definition: DefaultSettings.php:4303
The command line options to the tidy binary.
Definition: DefaultSettings.php:4321
Configuration for HTML postprocessing tool.
Definition: DefaultSettings.php:4297
The path to the tidy binary.
Definition: DefaultSettings.php:4309
Check if we are running under HHVM.
Definition: GlobalFunctions.php:2032
Returns true if tidy is usable.
Definition: TidySupport.php:70