wiki.techinc.nl

Thijs/wiki.techinc.nl

History

Timo Tijhof 50e7985d4d phpcs: Fix WhiteSpace.LanguageConstructSpacing warnings Squiz.WhiteSpace.LanguageConstructSpacing: Language constructs must be followed by a single space; expected "require_once expression" but found "require_once(expression)" It is a keyword (e.g. like `new`, `return` and `print`). As such the parentheses don't make sense. Per our code conventions, we use a space after keywords like these. We appeared to have an unwritten exception for `require` that doesn't make sense. About 60% of require/include usage was missing the space and/or had superfluous parentheses. It is as silly as print("foo") or return("foo"), it works because keywords have no significance for whitespace between it and the expression that follows, and since experessions can be wrapped in parentheses for clarity (e.g. when doing string concatenation or mathematical operations) the parenthesis before and after basiclaly just ignored. Change-Id: I2df2f80b8123714bea7e0771bf94b51ad5bb4b87	2013-05-09 05:56:26 +02:00
..
.gitignore	Revert "Creating new WMF 1.22wmf3 branch"	2013-04-29 19:20:01 +01:00
README	phpcs: Fix WhiteSpace.LanguageConstructSpacing warnings	2013-05-09 05:56:26 +02:00

Timo Tijhof 50e7985d4d phpcs: Fix WhiteSpace.LanguageConstructSpacing warnings

Squiz.WhiteSpace.LanguageConstructSpacing:
   Language constructs must be followed by a single space;
   expected "require_once expression" but found
   "require_once(expression)"

It is a keyword (e.g. like `new`, `return` and `print`). As
such the parentheses don't make sense.

Per our code conventions, we use a space after keywords like
these. We appeared to have an unwritten exception for `require`
that doesn't make sense. About 60% of require/include usage
was missing the space and/or had superfluous parentheses.

It is as silly as print("foo") or return("foo"), it works
because keywords have no significance for whitespace between
it and the expression that follows, and since experessions can
be wrapped in parentheses for clarity (e.g. when doing string
concatenation or mathematical operations) the parenthesis
before and after basiclaly just ignored.

Change-Id: I2df2f80b8123714bea7e0771bf94b51ad5bb4b87

2013-05-09 05:56:26 +02:00

.gitignore

Revert "Creating new WMF 1.22wmf3 branch"

2013-04-29 19:20:01 +01:00

README

phpcs: Fix WhiteSpace.LanguageConstructSpacing warnings

2013-05-09 05:56:26 +02:00

README

Extensions (such as the hieroglyphic module WikiHiero) are distributed
separately. Drop them into this extensions directory and enable as
per the extension's directions.

If you are a developer, you want to fetch the extension tree in another
directory and make a symbolic link:

 mediawiki/extensions$ ln -s ../../extensions-trunk/FooBarExt

The extensions are available through Git:
    https://gerrit.wikimedia.org/r/#/admin/projects/

or Subversion:
    https://svn.wikimedia.org/svnroot/mediawiki/trunk/extensions/

You can find documentation and additional extensions on MediaWiki website:
    https://www.mediawiki.org/wiki/Category:Extensions


Please note that under POSIX systems (Linux...), parent of a symbolic path
refers to the link source, NOT to the target! You should check the env
variable MW_INSTALL_PATH in case the extension is not in the default location.

The following code snippet lets you override the default path:

 $IP = getenv( 'MW_INSTALL_PATH' );
 if( $IP === false ) {
	$IP = __DIR__ . '/../..';
 }
 require_once "$IP/maintenance/Maintenance.php"; // a MediaWiki core file