18 if ( isset(
$params[
'placeholder-message'] ) ) {
19 $this->mPlaceholder = $this->
getMessage(
$params[
'placeholder-message'] )->parse();
20 } elseif ( isset(
$params[
'placeholder'] ) ) {
21 $this->mPlaceholder =
$params[
'placeholder'];
26 return isset( $this->mParams[
'size'] ) ? $this->mParams[
'size'] : 45;
30 $val = isset( $this->mParams[
'spellcheck'] ) ? $this->mParams[
'spellcheck'] : null;
31 if ( is_bool( $val ) ) {
33 return $val ===
true ?
'true' :
'false';
39 if ( isset( $this->mParams[
'persistent'] ) ) {
40 return $this->mParams[
'persistent'];
43 return !( isset( $this->mParams[
'type'] ) && $this->mParams[
'type'] ===
'password' );
60 if ( $this->mClass !==
'' ) {
63 if ( $this->mPlaceholder !==
'' ) {
67 # @todo Enforce pattern, step, required, readonly on the server side as
97 # Implement tiny differences between some field variants
98 # here, rather than creating a new class for each one which
99 # is essentially just a clone of this one.
100 if ( isset( $this->mParams[
'type'] ) ) {
101 switch ( $this->mParams[
'type'] ) {
114 $type = $this->mParams[
'type'];
129 if ( $this->mClass !==
'' ) {
132 if ( $this->mPlaceholder !==
'' ) {
136 # @todo Enforce pattern, step, required, readonly on the server side as
151 $attribs += OOUI\Element::configFromHtmlAttributes(
159 'name' => $this->mName,
166 return new OOUI\TextInputWidget(
$params );
getDataAttribs()
Returns an array of data-* attributes to add to the field.
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
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 one of or reset my talk my contributions etc etc otherwise the built in rate limiting checks are if enabled allows for interception of redirect as a string mapping parameter names to values & $type
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 after processing & $attribs