MediaWiki  1.28.0
DumpOutput.php
Go to the documentation of this file.
1 <?php
29 class DumpOutput {
30 
34  function writeOpenStream( $string ) {
35  $this->write( $string );
36  }
37 
41  function writeCloseStream( $string ) {
42  $this->write( $string );
43  }
44 
49  function writeOpenPage( $page, $string ) {
50  $this->write( $string );
51  }
52 
56  function writeClosePage( $string ) {
57  $this->write( $string );
58  }
59 
64  function writeRevision( $rev, $string ) {
65  $this->write( $string );
66  }
67 
72  function writeLogItem( $rev, $string ) {
73  $this->write( $string );
74  }
75 
81  function write( $string ) {
82  print $string;
83  }
84 
92  function closeRenameAndReopen( $newname ) {
93  }
94 
103  function closeAndRename( $newname, $open = false ) {
104  }
105 
111  function getFilenames() {
112  return null;
113  }
114 }
writeClosePage($string)
Definition: DumpOutput.php:56
writeCloseStream($string)
Definition: DumpOutput.php:41
closeAndRename($newname, $open=false)
Close the old file, and move it to a specified name.
Definition: DumpOutput.php:103
closeRenameAndReopen($newname)
Close the old file, move it to a specified name, and reopen new file with the old name...
Definition: DumpOutput.php:92
writeRevision($rev, $string)
Definition: DumpOutput.php:64
presenting them properly to the user as errors is done by the caller return true use this to change the list i e etc $rev
Definition: hooks.txt:1721
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
writeOpenStream($string)
Definition: DumpOutput.php:34
writeLogItem($rev, $string)
Definition: DumpOutput.php:72
getFilenames()
Returns the name of the file or files which are being written to, if there are any.
Definition: DumpOutput.php:111
do that in ParserLimitReportFormat instead use this to modify the parameters of the image and a DIV can begin in one section and end in another Make sure your code can handle that case gracefully See the EditSectionClearerLink extension for an example zero but section is usually empty its values are the globals values before the output is cached $page
Definition: hooks.txt:2491
writeOpenPage($page, $string)
Definition: DumpOutput.php:49
write($string)
Override to write to a different stream type.
Definition: DumpOutput.php:81