From 50e7985d4d5e9f70bd27e61d84d43514004f23da Mon Sep 17 00:00:00 2001 From: Timo Tijhof Date: Wed, 8 May 2013 01:00:15 +0200 Subject: 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 --- tests/selenium/SeleniumLoader.php | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'tests/selenium/SeleniumLoader.php') diff --git a/tests/selenium/SeleniumLoader.php b/tests/selenium/SeleniumLoader.php index 8d5e77139a7f..1a860f4b72af 100644 --- a/tests/selenium/SeleniumLoader.php +++ b/tests/selenium/SeleniumLoader.php @@ -2,8 +2,8 @@ class SeleniumLoader { static function load() { - require_once( 'Testing/Selenium.php' ); - require_once( 'PHPUnit/Framework.php' ); - require_once( 'PHPUnit/Extensions/SeleniumTestCase.php' ); + require_once 'Testing/Selenium.php'; + require_once 'PHPUnit/Framework.php'; + require_once 'PHPUnit/Extensions/SeleniumTestCase.php'; } } -- cgit v1.2.3