MediaWiki  1.33.0
Go to the documentation of this file.
1 <?php
7  public $options = [
8  'Bulgaria' => 'BGR',
9  'Burkina Faso' => 'BFA',
10  'Burundi' => 'BDI',
11  ];
22  new HTMLAutoCompleteSelectField( [ 'fieldname' => 'Test' ] );
23  }
31  function testGetAttributes() {
32  $field = new HTMLAutoCompleteSelectField( [
33  'fieldname' => 'Test',
34  'autocomplete' => $this->options,
35  ] );
37  $attributes = $field->getAttributes( [] );
38  $this->assertEquals( array_keys( $this->options ),
39  FormatJson::decode( $attributes['data-autocomplete'] ),
40  "The 'data-autocomplete' attribute encodes autocomplete option keys as a JSON array."
41  );
42  }
49  $params = [
50  'fieldname' => 'Test',
51  'autocomplete-data' => $this->options,
52  'options' => $this->options,
53  ];
55  $field = new HTMLAutoCompleteSelectField( $params );
56  $html = $field->getInputHTML( false );
57  $this->assertRegExp( '/select/', $html,
58  "When the 'options' parameter is set, the HTML includes a <select>" );
60  unset( $params['options'] );
61  $field = new HTMLAutoCompleteSelectField( $params );
62  $html = $field->getInputHTML( false );
63  $this->assertNotRegExp( '/select/', $html,
64  "When the 'options' parameter is not set, the HTML does not include a <select>" );
65  }
66 }
Definition: HTMLAutoCompleteSelectFieldTest.php:5
Definition: styleTest.css.php:44
Verify that attempting to instantiate an HTMLAutoCompleteSelectField without providing any autocomple...
Definition: HTMLAutoCompleteSelectFieldTest.php:21
Text field for selecting a value from a large list of possible values, with auto-completion and optio...
Definition: HTMLAutoCompleteSelectField.php:33
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
static decode( $value, $assoc=false)
Decodes a JSON string.
Definition: FormatJson.php:174
null means default in associative array with keys and values unescaped Should be merged with default with a value of false meaning to suppress the attribute in associative array with keys and values unescaped noclasses just before the function returns a value If you return an< a > element with HTML attributes $attribs and contents $html will be returned If you return $ret will be returned and may include noclasses & $html
Definition: hooks.txt:1985
Test that the optional select dropdown is included or excluded based on the presence or absence of th...
Definition: HTMLAutoCompleteSelectFieldTest.php:48
Definition: MediaWikiTestCase.php:17
Verify that the autocomplete options are correctly encoded as the 'data-autocomplete' attribute of th...
Definition: HTMLAutoCompleteSelectFieldTest.php:31
Definition: HTMLAutoCompleteSelectFieldTest.php:7
Using a hook running we can avoid having all this option specific stuff in our mainline code Using the function We ve cleaned up the code here by removing clumps of infrequently used code and moving them off somewhere else It s much easier for someone working with this code to see what s _really_ going and make changes or fix bugs In we can take all the code that deals with the little used title reversing options(say) and put it in one place. Instead of having little title-reversing if-blocks spread all over the codebase in showAnArticle