MediaWiki  1.28.1
Go to the documentation of this file.
1 <?php
10  public function testPrefixes() {
11  $main = new ApiMain( new FauxRequest() );
12  $query = new ApiQuery( $main, 'foo', 'bar' );
13  $moduleManager = $query->getModuleManager();
15  $modules = $moduleManager->getNames();
16  $prefixes = [];
18  foreach ( $modules as $name ) {
19  $module = $moduleManager->getModule( $name );
20  $class = get_class( $module );
22  $prefix = $module->getModulePrefix();
23  if ( $prefix !== '' && isset( $prefixes[$prefix] ) ) {
24  $this->fail( "Module prefix '{$prefix}' is shared between {$class} and {$prefixes[$prefix]}" );
25  }
26  $prefixes[$module->getModulePrefix()] = $class;
27  }
28  $this->assertTrue( true ); // dummy call to make this test non-incomplete
29  }
30 }
null for the local wiki Added should default to null in handler for backwards compatibility add a value to it if you want to add a cookie that have to vary cache options can modify $query
Definition: hooks.txt:1555
This is the main API class, used for both external and internal processing.
Definition: ApiMain.php:43
Checks that all API query modules, core and extensions, have unique prefixes.
This is the main query class.
Definition: ApiQuery.php:38
This document is intended to provide useful advice for parties seeking to redistribute MediaWiki to end users It s targeted particularly at maintainers for Linux since it s been observed that distribution packages of MediaWiki often break We ve consistently had to recommend that users seeking support use official tarballs instead of their distribution s and this often solves whatever problem the user is having It would be nice if this could such as
Definition: distributors.txt:9
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
Allows to change the fields on the form that will be generated $name
Definition: hooks.txt:300