MediaWiki  1.33.0
ReplaceTextUtils.php
Go to the documentation of this file.
1 <?php
21 use \MediaWiki\MediaWikiServices;
22 
23 class ReplaceTextUtils {
24 
31  public static function link( Title $title, $text = null ) {
32  if ( method_exists( '\MediaWiki\MediaWikiServices', 'getLinkRenderer' ) ) {
33  $linkRenderer = MediaWikiServices::getInstance()->getLinkRenderer();
34  if ( class_exists( 'HtmlArmor' ) && !is_null( $text ) ) {
35  $text = new HtmlArmor( $text );
36  }
37  return $linkRenderer->makeLink( $title, $text );
38  };
39  return Linker::link( $title, $text );
40  }
41 }
HtmlArmor
Marks HTML that shouldn't be escaped.
Definition: HtmlArmor.php:28
$linkRenderer
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 after in associative array form before processing starts Return false to skip default processing and return $ret $linkRenderer
Definition: hooks.txt:1985
php
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
ReplaceTextUtils\link
static link(Title $title, $text=null)
Shim for compatibility.
Definition: ReplaceTextUtils.php:31
$title
namespace and then decline to actually register it file or subcat img or subcat $title
Definition: hooks.txt:925
Linker\link
static link( $target, $html=null, $customAttribs=[], $query=[], $options=[])
This function returns an HTML link to the given target.
Definition: Linker.php:84
Title
Represents a title within MediaWiki.
Definition: Title.php:40
ReplaceTextUtils
Definition: ReplaceTextUtils.php:23
MediaWikiServices
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 MediaWikiServices
Definition: injection.txt:23