MediaWiki REL1_31
CommentStoreComment.php
Go to the documentation of this file.
1<?php
29
31 public $id;
32
34 public $text;
35
37 public $message;
38
40 public $data;
41
49 public function __construct( $id, $text, Message $message = null, array $data = null ) {
50 $this->id = $id;
51 $this->text = $text;
52 $this->message = $message ?: new RawMessage( '$1', [ $text ] );
53 $this->data = $data;
54 }
55
65 public static function newUnsavedComment( $comment, array $data = null ) {
67
68 if ( $comment instanceof CommentStoreComment ) {
69 return $comment;
70 }
71
72 if ( $data !== null ) {
73 foreach ( $data as $k => $v ) {
74 if ( substr( $k, 0, 1 ) === '_' ) {
75 throw new InvalidArgumentException( 'Keys in $data beginning with "_" are reserved' );
76 }
77 }
78 }
79
80 if ( $comment instanceof Message ) {
81 $message = clone $comment;
82 $text = $message->inLanguage( $wgContLang ) // Avoid $wgForceUIMsgAsContentMsg
83 ->setInterfaceMessageFlag( true )
84 ->text();
85 return new CommentStoreComment( null, $text, $message, $data );
86 } else {
87 return new CommentStoreComment( null, $comment, null, $data );
88 }
89 }
90}
CommentStoreComment represents a comment stored by CommentStore.
string $text
Text version of the comment.
static newUnsavedComment( $comment, array $data=null)
Create a new, unsaved CommentStoreComment.
int null $id
Comment ID, if any.
__construct( $id, $text, Message $message=null, array $data=null)
Message $message
Message version of the comment.
array null $data
Structured data of the comment.
The Message class provides methods which fulfil two basic services:
Definition Message.php:159
inLanguage( $lang)
Request the message in any language that is supported.
Definition Message.php:728
Variant of the Message class.
this class mediates it Skin Encapsulates a look and feel for the wiki All of the functions that render HTML and make choices about how to render it are here and are called from various other places when and is meant to be subclassed with other skins that may override some of its functions The User object contains a reference to a and so rather than having a global skin object we just rely on the global User and get the skin with $wgUser and also has some character encoding functions and other locale stuff The current user interface language is instantiated as and the local content language as $wgContLang
Definition design.txt:57
when a variable name is used in a it is silently declared as a new local masking the global
Definition design.txt:95
design txt This is a brief overview of the new design More thorough and up to date information is available on the documentation wiki at etc Handles the details of getting and saving to the user table of the and dealing with sessions and cookies OutputPage Encapsulates the entire HTML page that will be sent in response to any server request It is used by calling its functions to add text
Definition design.txt:18
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
the array() calling protocol came about after MediaWiki 1.4rc1.
either a unescaped string or a HtmlArmor object after in associative array form externallinks including delete and has completed for all link tables whether this was an auto creation default is conds Array Extra conditions for the No matching items in log is displayed if loglist is empty msgKey Array If you want a nice box with a message
Definition hooks.txt:2163
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:37
This document describes the state of Postgres support in and is fairly well maintained The main code is very well while extensions are very hit and miss it is probably the most supported database after MySQL Much of the work in making MediaWiki database agnostic came about through the work of creating Postgres but without copying over all the usage comments General notes on the but these can almost always be programmed around *Although Postgres has a true BOOLEAN boolean columns are always mapped to as the code does not always treat the column as a and VARBINARY columns should simply be TEXT The only exception is when VARBINARY is used to store true binary data
Definition postgres.txt:37