Difference between revisions of "Joomla CodeSniffer"

From Joomla! Documentation

m (Might be a dev dependency. Hence --dev after composer global require)
(Removed dead URLs to screenshots.)
 
(2 intermediate revisions by the same user not shown)
Line 21: Line 21:
  
 
<translate>
 
<translate>
==1. Installation of PHP Code Sniffer (phpcs)== <!--T:9-->
+
==Installation of PHP Code Sniffer (phpcs)== <!--T:9-->
 
</translate>
 
</translate>
 
<translate>
 
<translate>
Line 27: Line 27:
 
</translate>
 
</translate>
 
<translate><!--T:11--> PHP Code Sniffer is available via Composer. It can be installed system-wide with the following command:</translate><br />
 
<translate><!--T:11--> PHP Code Sniffer is available via Composer. It can be installed system-wide with the following command:</translate><br />
<tt>composer global require --dev squizlabs/php_codesniffer "~3.5"</tt>
+
''composer global require --dev squizlabs/php_codesniffer "~3.5"''
 
<translate>
 
<translate>
 
<!--T:12-->
 
<!--T:12-->
On '''Linux''' PHP Code Sniffer (phpcs) will be installed under your user folder:</translate>  
+
On '''Linux''' PHP Code Sniffer (phpcs) will be installed under your user folder:</translate>
* <translate><!--T:13--> Symbolic Link:</translate> <tt>~/.composer/vendor/bin/phpcs</tt>
+
* <translate><!--T:13--> Symbolic Link:</translate> ''~/.composer/vendor/bin/phpcs''
* <translate><!--T:14--> The file:</translate> <tt>~/.composer/vendor/squizlabs/php_codesniffer/scripts/phpcs</tt>
+
* <translate><!--T:14--> The file:</translate> ''~/.composer/vendor/squizlabs/php_codesniffer/scripts/phpcs''
<translate><!--T:76--> To create that symbolic link, use on the command line: <code></translate>
+
<translate><!--T:76--> To create that symbolic link, use on the command line: </translate>
$ sudo ln -s ~/.config/composer/vendor/squizlabs/php_codesniffer/scripts /usr/bin/phpcs
+
''$ sudo ln -s ~/.config/composer/vendor/squizlabs/php_codesniffer/scripts /usr/bin/phpcs''
</code>
 
  
 
<translate><!--T:15--> or (for example OpenSuse)</translate>
 
<translate><!--T:15--> or (for example OpenSuse)</translate>
* <translate><!--T:16--> Symbolic Link:</translate> <tt>~/.config/composer/vendor/bin/phpcs</tt>
+
* <translate><!--T:16--> Symbolic Link:</translate> ''~/.config/composer/vendor/bin/phpcs''
* <translate><!--T:17--> The file:</translate> <tt>~/.config/composer/vendor/squizlabs/php_codesniffer/scripts/phpcs</tt>
+
* <translate><!--T:17--> The file:</translate> ''~/.config/composer/vendor/squizlabs/php_codesniffer/scripts/phpcs''
  
 
<translate><!--T:18--> On '''Windows''' PHP Code Sniffer (phpcs) will be installed under your user folder:</translate>
 
<translate><!--T:18--> On '''Windows''' PHP Code Sniffer (phpcs) will be installed under your user folder:</translate>
* <translate><!--T:19--> Symbolic Link:</translate> <tt>c:\Users\Username\AppData\Roaming\Composer\vendor\bin\phpcs</tt>
+
* <translate><!--T:19--> Symbolic Link:</translate> ''c:\Users\Username\AppData\Roaming\Composer\vendor\bin\phpcs''
* <translate><!--T:20--> The file:</translate> <tt>c:\Users\Username\AppData\Roaming\Composer\vendor\squizlabs\php_codesniffer\scripts\phpcs</tt>
+
* <translate><!--T:20--> The file:</translate> ''c:\Users\Username\AppData\Roaming\Composer\vendor\squizlabs\php_codesniffer\scripts\phpcs''
  
 
<translate>
 
<translate>
 
 
=== Add composer bin directory to your $PATH === <!--T:21-->
 
=== Add composer bin directory to your $PATH === <!--T:21-->
 
</translate>
 
</translate>
 
<translate>
 
<translate>
 
<!--T:22-->
 
<!--T:22-->
In order to execute PHP Code sniffer from anywhere on Linux or Mac command line you have to add <tt>.composer/vendor/bin</tt> to your $PATH variable.</translate>
+
In order to execute PHP Code sniffer from anywhere on Linux or Mac command line you have to add ''.composer/vendor/bin'' to your $PATH variable.</translate>
 
<translate>
 
<translate>
 
<!--T:23-->
 
<!--T:23-->
Line 57: Line 55:
  
 
<translate><!--T:24--> Add the following line to the file:</translate>
 
<translate><!--T:24--> Add the following line to the file:</translate>
<tt>export PATH=$PATH:~/.composer/vendor/bin</tt>
+
''export PATH=$PATH:~/.composer/vendor/bin''
  
 
<translate><!--T:25--> Alternatively you can also create a symbolic link in the bin folder:</translate>
 
<translate><!--T:25--> Alternatively you can also create a symbolic link in the bin folder:</translate>
<tt>ln -s ~/.composer/vendor/bin/phpcs /usr/local/bin/phpcs</tt>
+
''ln -s ~/.composer/vendor/bin/phpcs /usr/local/bin/phpcs''
  
 
<translate>
 
<translate>
 
+
==Install Joomla Coding Standards== <!--T:26-->
==2. Install Joomla Coding Standards== <!--T:26-->
 
 
</translate>
 
</translate>
 
<translate><!--T:27--> In order to have PHP Code Sniffer (phpcs) sniffing your Joomla projects for the right code style, you have to install the Joomla Coding Standards.</translate>
 
<translate><!--T:27--> In order to have PHP Code Sniffer (phpcs) sniffing your Joomla projects for the right code style, you have to install the Joomla Coding Standards.</translate>
  
 
<translate><!--T:28--> Using composer we can execute:</translate>
 
<translate><!--T:28--> Using composer we can execute:</translate>
<tt>composer global require --dev joomla/coding-standards "~3.0@alpha"</tt>
+
''composer global require --dev joomla/coding-standards "~3.0@alpha"''
  
<translate><!--T:29--> Notice that it says <tt>@alpha</tt>, that is because the coding standard is still in alpha state and we need to allow the installation of alpha status code. If we do not include the @alpha the coding standards will not install and throw this error.</translate>
+
<translate><!--T:29--> Notice that it says ''@alpha'', that is because the coding standard is still in alpha state and we need to allow the installation of alpha status code. If we do not include the @alpha the coding standards will not install and throw this error.</translate>
  
 
<pre>
 
<pre>
 
Your requirements could not be resolved to an installable set of packages.
 
Your requirements could not be resolved to an installable set of packages.
  
  Problem 1
+
Problem 1
    - The requested package joomla/coding-standards ~3.0 is satisfiable by joomla/coding-standards[3.0.0-alpha, 3.0.0-alpha2, 3.x-dev] but these conflict with your requirements or minimum-stability.
+
- The requested package joomla/coding-standards ~3.0 is satisfiable by joomla/coding-standards[3.0.0-alpha, 3.0.0-alpha2, 3.x-dev] but these conflict with your requirements or minimum-stability.
 
</pre>
 
</pre>
  
Line 83: Line 80:
  
 
'''Mac / Linux'''
 
'''Mac / Linux'''
~/.composer/vendor/joomla/coding-standards/
 
  
~/.config/composer/vendor/joomla/coding-standards/
+
''~/.composer/vendor/joomla/coding-standards/''
 +
and
 +
''~/.config/composer/vendor/joomla/coding-standards/''
 +
 
 
'''Windows'''
 
'''Windows'''
c:\Users\Username\AppData\Roaming\Composer\vendor\joomla\coding-standards\
+
 
 +
''c:\Users\Username\AppData\Roaming\Composer\vendor\joomla\coding-standards\''
 +
 
 
<translate><!--T:31--> This is using Composer on Windows.</translate>
 
<translate><!--T:31--> This is using Composer on Windows.</translate>
  
<translate><!--T:32--> If you can't find it in any of the above folders, note that the folder you are looking for ends with '''\joomla\coding-standards\'''</translate>
+
<translate><!--T:32--> If you can't find it in any of the above folders, note that the folder you are looking for ends with ''\joomla\coding-standards\''.</translate>
 
<translate>
 
<translate>
 
<!--T:33-->
 
<!--T:33-->
Line 97: Line 98:
 
<translate><!--T:34-->
 
<translate><!--T:34-->
 
'''Install Joomla Coding Standards'''
 
'''Install Joomla Coding Standards'''
# Check if certain paths are already set by running <tt>phpcs --config-show</tt>
+
# Check if certain paths are already set by running ''phpcs --config-show''
# You can get an answer that looks like this: <tt>installed_paths: /path/to/installation</tt>
+
# You can get an answer that looks like this: ''installed_paths: /path/to/installation''
 
# In step 2, if you see the '''installed_paths''' you need to copy that
 
# In step 2, if you see the '''installed_paths''' you need to copy that
# Set the Joomla Coding Standards path in phpcs by executing <tt>phpcs --config-set installed_paths /Users/user/.composer/vendor/joomla/coding-standards</tt>. If you copied any paths in step 2, include them here as well by separating them with a comma. The command looks like <tt>phpcs --config-set installed_paths [/to/path1],[/to/path2],[/Users/user/.composer/vendor/joomla/coding-standards]</tt>
+
# Set the Joomla Coding Standards path in phpcs by executing ''phpcs --config-set installed_paths /Users/user/.composer/vendor/joomla/coding-standards''. If you copied any paths in step 2, include them here as well by separating them with a comma. The command looks like ''phpcs --config-set installed_paths [/to/path1],[/to/path2],[/Users/user/.composer/vendor/joomla/coding-standards]''
# Verify the path is set correctly by running <tt>phpcs --config-show</tt>
+
# Verify the path is set correctly by running ''phpcs --config-show''
# Verify that phpcs can see the Joomla codestyle by running <tt>phpcs -i</tt>
+
# Verify that phpcs can see the Joomla codestyle by running ''phpcs -i''
# The output should look like this: <tt>The installed coding standards are MySource, PEAR, PHPCS, PSR1, PSR2, Squiz, Zend and Joomla</tt></translate>
+
# The output should look like this: ''The installed coding standards are MySource, PEAR, PHPCS, PSR1, PSR2, Squiz, Zend and Joomla''</translate>
 
<translate>
 
<translate>
  
Line 109: Line 110:
 
</translate>
 
</translate>
 
<translate><!--T:36--> You invoke the custom standard by</translate>
 
<translate><!--T:36--> You invoke the custom standard by</translate>
<tt>phpcs --standard=Joomla file/to/sniff</tt>
+
''phpcs --standard=Joomla file/to/sniff''
  
 
<translate><!--T:37--> To test a platform file using the provided platform coding standards, use</translate>
 
<translate><!--T:37--> To test a platform file using the provided platform coding standards, use</translate>
<tt>phpcs --standard=build/phpcs/Joomla path/to/file/or/folder</tt>
+
''phpcs --standard=build/phpcs/Joomla path/to/file/or/folder''
  
<translate><!--T:38--> Further documentation on the use of phpcs can be found at: [http://pear.php.net/package/PHP_CodeSniffer/docs]</translate>
+
<translate><!--T:38--> Further documentation on the use of phpcs can be found at the [https://pear.php.net/package/PHP_CodeSniffer/docs pear.php.net website].</translate>
  
 
<translate>
 
<translate>
==3. IDE Integration== <!--T:39-->
+
==IDE Integration== <!--T:39-->
 
</translate>
 
</translate>
 
<translate><!--T:40--> Everybody loves the console. It is, with no doubt, the most effective way to do whatever you need to do. Sometimes even Linux gurus need a little bit of comfort.</translate>
 
<translate><!--T:40--> Everybody loves the console. It is, with no doubt, the most effective way to do whatever you need to do. Sometimes even Linux gurus need a little bit of comfort.</translate>
Line 126: Line 127:
 
=== PhpStorm === <!--T:42-->
 
=== PhpStorm === <!--T:42-->
 
</translate>
 
</translate>
<translate><!--T:43--> Code Sniffer is supported out of the box in PhpStorm. Go to Settings and under Editor {{rarr}} Inspections you will see the list of sniffers you have installed.</translate>
+
<translate><!--T:43--> Code Sniffer is supported out of the box in PhpStorm. Go to Settings and under {{rarr|Editor,Inspections}} you will see the list of sniffers you have installed.</translate>
 
<translate>
 
<translate>
 
==== Set Path to Code Sniffer ==== <!--T:44-->
 
==== Set Path to Code Sniffer ==== <!--T:44-->
Line 158: Line 159:
  
 
<translate>
 
<translate>
 
 
==== PHP PSR-0, PSR-1 and PSR-2 ==== <!--T:48-->
 
==== PHP PSR-0, PSR-1 and PSR-2 ==== <!--T:48-->
 
</translate>
 
</translate>
Line 192: Line 192:
 
* Choose a "Name", "Group" and "Description".
 
* Choose a "Name", "Group" and "Description".
 
* Click "Output Filters"
 
* Click "Output Filters"
** Click "Add...", Choose a name and enter under "Regular expression to match output" the value: <tt>$FILE_PATH$:$LINE$:$COLUMN$</tt>
+
** Click "Add...", Choose a name and enter under "Regular expression to match output" the value: ''$FILE_PATH$:$LINE$:$COLUMN$''
 
* "Program": Search for the phpcs executable on your system. You have to set the path to the ''phpcs.bat'' from the installed PHP_CodeSniffer PEAR package
 
* "Program": Search for the phpcs executable on your system. You have to set the path to the ''phpcs.bat'' from the installed PHP_CodeSniffer PEAR package
 
** For Unix based systems, the path is something like /usr/bin/phpcs
 
** For Unix based systems, the path is something like /usr/bin/phpcs
 
** In XAMPP (windows), you can find the file in the PHP root folder (e.g. C:\xampp\php\phpcs.bat)
 
** In XAMPP (windows), you can find the file in the PHP root folder (e.g. C:\xampp\php\phpcs.bat)
 
* "Parameters":
 
* "Parameters":
** <tt>--standard=<path/to/joomla-platform>/build/phpcs/Joomla</tt> The path to the Joomla! coding standards.
+
** ''--standard=<path/to/joomla-platform>/build/phpcs/Joomla'' The path to the Joomla! coding standards.
** <tt>--report=emacs</tt> The will generate a simple list containing links to the error files
+
** ''--report=emacs'' The will generate a simple list containing links to the error files
** Optionally you may want to specify <tt>-p</tt> for "progress" or <tt>-n</tt> for "errors only".
+
** Optionally you may want to specify ''-p'' for "progress" or ''-n'' for "errors only".
** The last parameter has to be <tt>$FilePath$</tt> specifying the file or folder you want to sniff.</translate>
+
** The last parameter has to be ''$FilePath$'' specifying the file or folder you want to sniff.</translate>
  
 
<translate><!--T:57--> A typical "Parameters" line on a Linux system might look like this:</translate>
 
<translate><!--T:57--> A typical "Parameters" line on a Linux system might look like this:</translate>
<pre>-np --standard=/home/elkuku/libs/joomla/build/phpcs/Joomla --report=emacs $FilePath$</pre>
+
 
 +
''-np --standard=/home/elkuku/libs/joomla/build/phpcs/Joomla --report=emacs $FilePath$''
  
 
<translate><!--T:58--> You may now right click any file or folder and choose the sniffer from the context menu or add a new tool bar button with a nice Joomla! logo</translate> [[File:icon-16-joomla.png]].
 
<translate><!--T:58--> You may now right click any file or folder and choose the sniffer from the context menu or add a new tool bar button with a nice Joomla! logo</translate> [[File:icon-16-joomla.png]].
Line 214: Line 215:
 
<translate><!--T:61-->
 
<translate><!--T:61-->
 
# Start your Netbeans IDE
 
# Start your Netbeans IDE
# Open Tools => Options => PHP => Code Analysis => Code Sniffer
+
# Open {{rarr|Tools,Options,PHP,Code Analysis,Code Sniffer}}
 
# You have to set the path to ''phpcs.bat'' from the installed PHP_CodeSniffer PEAR package
 
# You have to set the path to ''phpcs.bat'' from the installed PHP_CodeSniffer PEAR package
 
#* For Unix based systems the path is something like /usr/bin/phpcs
 
#* For Unix based systems the path is something like /usr/bin/phpcs
Line 220: Line 221:
 
# As "Default Standard," choose "Joomla" to use the Joomla! standard
 
# As "Default Standard," choose "Joomla" to use the Joomla! standard
 
# Now you can click ''OK'' to start sniffing
 
# Now you can click ''OK'' to start sniffing
# Open from the top menu Source => Inspect...
+
# Open from the top menu {{rarr|Source,Inspect}}
 
# Enjoy</translate>
 
# Enjoy</translate>
  
Line 230: Line 231:
 
<translate><!--T:63-->
 
<translate><!--T:63-->
 
Installation is a breeze and follows the usual pattern:
 
Installation is a breeze and follows the usual pattern:
# <tt>Help => Install New Software...</tt>
+
# {{rarr|Help,Install New Software}}
# <tt>Work with:</tt> Fill in one of the update site URLs found here: http://www.phpsrc.org/eclipse/pti/
+
# ''Work with:'' Fill in one of the update site URLs found here: http://www.phpsrc.org/eclipse/pti/
 
# Select the desired tools
 
# Select the desired tools
 
# Restart Eclipse.</translate>
 
# Restart Eclipse.</translate>
Line 238: Line 239:
 
<translate><!--T:65--> You are now able to sniff for code violations against common standards like PEAR or Zend etc.</translate>
 
<translate><!--T:65--> You are now able to sniff for code violations against common standards like PEAR or Zend etc.</translate>
  
<translate><!--T:66--> To sniff against your own standards, specify their location and activate them (see screen shot 2)</translate>
+
<translate><!--T:66--> To sniff against your own standards, specify their location and activate them:</translate>
 
<translate><!--T:67-->
 
<translate><!--T:67-->
# <tt>Window => Preferences</tt>
+
# {{rarr|Window,Preferences}}
# <tt>PHP Tools => PHP CodeSniffer</tt></translate>
+
# {{rarr|PHP Tools,PHP CodeSniffer}}</translate>
  
 
<translate><!--T:68--> Happy sniffing.</translate>
 
<translate><!--T:68--> Happy sniffing.</translate>
  
 
<translate>
 
<translate>
 
 
=== Geany === <!--T:69-->
 
=== Geany === <!--T:69-->
 
</translate>
 
</translate>
 
<translate><!--T:70-->
 
<translate><!--T:70-->
* Open a PHP file. (Otherwise the build menu is not accessible.) See this [http://static.xscreenshot.com/2016/07/13/08/screen_6bc0692cf995702a1e379b39643d0c2d Screenshot]
+
* Open a PHP file. (Otherwise the build menu is not accessible.)
 
* On the top menu, select Build->Set Build Commands.
 
* On the top menu, select Build->Set Build Commands.
* Select the second field and name it as you wish. Enter this code in the Command: <code>phpcs --standard=Joomla "%f" | sed -e 's/^/%f |/' | egrep 'WARNING|ERROR'</code>
+
* Select the second field and name it as you wish. Enter this code in the Command: ''phpcs --standard=Joomla "%f" | sed -e 's/^/%f |/' | egrep 'WARNING|ERROR'''
* Enter this code in the Error Regular Expression field: <code>(.+) [|]\s+([0-9]+)</code> See this  [http://view.xscreenshot.com/ef00820cf7c017ce659c8e9f0b02d3ae Screenshot]
+
* Enter this code in the Error Regular Expression field: ''(.+) [|]\s+([0-9]+)''
* Select OK.
+
* Select ''OK''.
* If the Message Window is not open, display it by selecting it in the top View menu.
+
* If the Message Window is not open, display it by selecting it in the top ''View'' menu.
* When viewing any PHP file, press F9 to see the errors found. [http://view.xscreenshot.com/8704b9fd1bda3f841364a0ffa28a54ae Screenshot]</translate>
+
* When viewing any PHP file, press F9 to see the errors found.</translate>
  
 
<translate>
 
<translate>
 
 
=== Atom === <!--T:78-->
 
=== Atom === <!--T:78-->
 
</translate>
 
</translate>
Line 265: Line 264:
 
<!--T:79-->
 
<!--T:79-->
 
* Install phpcs and the Joomla standards as described above.
 
* Install phpcs and the Joomla standards as described above.
* In '''Atom > Preferences > Install''' install '''linter-phpcs''' and all its requirements.
+
* In {{rarr|Atom,Preferences,Install}} install ''linter-phpcs'' and all its requirements.
* In '''Atom > Preferences > Packages > linter-phpcs > Settings''' adjust
+
* In {{rarr|Atom,Preferences,Packages,linter-phpcs,Settings}} adjust
 
** '''Executable Path''' to the path of your phpcs
 
** '''Executable Path''' to the path of your phpcs
 
** '''Code Standard Or Config File''': Joomla
 
** '''Code Standard Or Config File''': Joomla
Line 275: Line 274:
 
=== References === <!--T:71-->
 
=== References === <!--T:71-->
 
</translate>
 
</translate>
* https://github.com/joomla/coding-standards - <translate><!--T:72--> Joomla! Coding Standards</translate>
+
* [https://github.com/joomla/coding-standards Joomla! Coding Standards]
* http://www.phpsrc.org/ <translate><!--T:73--> PTI - PHP tools integration for Eclipse</translate>
+
* [https://www.phpsrc.org/ PTI - PHP tools integration for Eclipse]
* http://sourceforge.net/projects/phpmdnb/ <translate><!--T:74--> Netbeans plugin</translate>
+
* [https://sourceforge.net/projects/phpmdnb/ Netbeans plugin]
* http://hakre.wordpress.com/2010/03/06/php-code-sniffer-eclipse-and-wordpress/ - <translate><!--T:75--> Excellent article. Just change "Wordpress" for "Joomla!" ;)</translate>
+
* https://hakre.wordpress.com/2010/03/06/php-code-sniffer-eclipse-and-wordpress/ - <translate><!--T:75--> Excellent article. Just change ''Wordpress'' for ''Joomla'' ;)</translate>
  
 
<noinclude>
 
<noinclude>

Latest revision as of 15:57, 5 July 2023

Other languages:
English • ‎Türkçe • ‎français • ‎русский

A Nose For Joomla[edit]

This is a custom coding standard for the PHP CodeSniffer that attempts to codify and enforce the Joomla coding standards. This article covers how to set the automatic code style checker. It consists of three steps:

  1. Install PHP CodeSniffer (phpcs).
  2. Clone the Joomla Code Style (for use with for phpcs).
  3. Configure your IDE to work with PHP CodeSniffer and Joomla Code Style.
PHP Code Sniffer in action

Why?[edit]

  • Coherent and consistent coding practice makes the files look more professional. Conflicting styles in the same project (or worse, the same file) not only look sloppy, they encourage further sloppiness.
  • When all code complies with the same standard, bad code is easier for everyone to spot.
  • It makes it easier for someone new to a particular file in the project to find and fix errors or extend functionality.
  • If there is no consistent standard maintained, sometimes developers will reformat the code to suit themselves. This causes a wide range of changes in the code repository. If there is a later problem, a significant change could be lost in the chaff produced by a diff.

Installation of PHP Code Sniffer (phpcs)[edit]

Composer[edit]

PHP Code Sniffer is available via Composer. It can be installed system-wide with the following command:
composer global require --dev squizlabs/php_codesniffer "~3.5" On Linux PHP Code Sniffer (phpcs) will be installed under your user folder:

  • Symbolic Link: ~/.composer/vendor/bin/phpcs
  • The file: ~/.composer/vendor/squizlabs/php_codesniffer/scripts/phpcs

To create that symbolic link, use on the command line: $ sudo ln -s ~/.config/composer/vendor/squizlabs/php_codesniffer/scripts /usr/bin/phpcs

or (for example OpenSuse)

  • Symbolic Link: ~/.config/composer/vendor/bin/phpcs
  • The file: ~/.config/composer/vendor/squizlabs/php_codesniffer/scripts/phpcs

On Windows PHP Code Sniffer (phpcs) will be installed under your user folder:

  • Symbolic Link: c:\Users\Username\AppData\Roaming\Composer\vendor\bin\phpcs
  • The file: c:\Users\Username\AppData\Roaming\Composer\vendor\squizlabs\php_codesniffer\scripts\phpcs

Add composer bin directory to your $PATH[edit]

In order to execute PHP Code sniffer from anywhere on Linux or Mac command line you have to add .composer/vendor/bin to your $PATH variable. To do this persistent edit your shells start file, like your .profile or .bash_profile file depending which shell you are using (echo $SHELL shows you which one you are using).

Add the following line to the file: export PATH=$PATH:~/.composer/vendor/bin

Alternatively you can also create a symbolic link in the bin folder: ln -s ~/.composer/vendor/bin/phpcs /usr/local/bin/phpcs

Install Joomla Coding Standards[edit]

In order to have PHP Code Sniffer (phpcs) sniffing your Joomla projects for the right code style, you have to install the Joomla Coding Standards.

Using composer we can execute: composer global require --dev joomla/coding-standards "~3.0@alpha"

Notice that it says @alpha, that is because the coding standard is still in alpha state and we need to allow the installation of alpha status code. If we do not include the @alpha the coding standards will not install and throw this error.

Your requirements could not be resolved to an installable set of packages.

Problem 1
 - The requested package joomla/coding-standards ~3.0 is satisfiable by joomla/coding-standards[3.0.0-alpha, 3.0.0-alpha2, 3.x-dev] but these conflict with your requirements or minimum-stability.

Once the installation is done the coding standard will be installed in the global composer folder. The location of this folder depends on your operating system. Some popular locations are:

Mac / Linux

~/.composer/vendor/joomla/coding-standards/ and ~/.config/composer/vendor/joomla/coding-standards/

Windows

c:\Users\Username\AppData\Roaming\Composer\vendor\joomla\coding-standards\

This is using Composer on Windows.

If you can't find it in any of the above folders, note that the folder you are looking for ends with \joomla\coding-standards\. Finally we need to tell Code Sniffer that the Joomla coding standards exist.

Install Joomla Coding Standards

  1. Check if certain paths are already set by running phpcs --config-show
  2. You can get an answer that looks like this: installed_paths: /path/to/installation
  3. In step 2, if you see the installed_paths you need to copy that
  4. Set the Joomla Coding Standards path in phpcs by executing phpcs --config-set installed_paths /Users/user/.composer/vendor/joomla/coding-standards. If you copied any paths in step 2, include them here as well by separating them with a comma. The command looks like phpcs --config-set installed_paths [/to/path1],[/to/path2],[/Users/user/.composer/vendor/joomla/coding-standards]
  5. Verify the path is set correctly by running phpcs --config-show
  6. Verify that phpcs can see the Joomla codestyle by running phpcs -i
  7. The output should look like this: The installed coding standards are MySource, PEAR, PHPCS, PSR1, PSR2, Squiz, Zend and Joomla

Usage[edit]

You invoke the custom standard by phpcs --standard=Joomla file/to/sniff

To test a platform file using the provided platform coding standards, use phpcs --standard=build/phpcs/Joomla path/to/file/or/folder

Further documentation on the use of phpcs can be found at the pear.php.net website.

IDE Integration[edit]

Everybody loves the console. It is, with no doubt, the most effective way to do whatever you need to do. Sometimes even Linux gurus need a little bit of comfort.

Fortunately there is a plug-in available for PhpStorm, Eclipse and Netbeans that integrates the CodeSniffer into your favourite IDE, so any coding standard violations are shown like "normal" errors.

PhpStorm[edit]

Code Sniffer is supported out of the box in PhpStorm. Go to Settings and under Editor  Inspections you will see the list of sniffers you have installed.

Set Path to Code Sniffer[edit]

  1. Open Settings (CTRL-ALT-S / CMD-,)
  2. Go to Languages & Frameworks
  3. Click on PHP
  4. Click on Quality Tools
  5. Click on PHP cs fixer dropdown arrow
  6. The configuration is set to Local by default
  7. Click on the 3 dots behind it to open the configuration screen
  8. The first option is the PHP Code Sniffer (phpcs) path
  9. Click on the 3 dots behind the path to select the location of the phpcs file. See above on where phpcs may be installed on your site
  10. Click on Validate to make sure the path is correct and phpcs is working
  11. Click OK
Activating the Joomla Code Style[edit]
  1. Open Settings (CTRL-ALT-S / CMD-,)
  2. Go to Editor
  3. Click on Inspections
  4. In the list, go to PHP
  5. Click on PHP Code Sniffer Validation
  6. Click on the check box behind it to activate it
  7. Click the Reload button (2 arrows) to force a reload of rules from disk
  8. Joomla should now be available in the list. See following image:
    PHPStorm CodeSniffer
  9. Click OK

PHP PSR-0, PSR-1 and PSR-2[edit]

Using PHP PSR-1 and PSR-2 Sniff[edit]

A CodeSniffer sniff to check against the PSR-x Coding Standard can be used as well. In that case you can select a different standard than Joomla.

Using Joomla Code style[edit]

It's nice to be able to check that the standards are respected. It's even nicer if PhpStorm helps you format properly too as you are coding. To use the Joomla code style in PhpStorm

  1. Open Settings (CTRL-ALT-S / CMD-,)
  2. Go to Editor
  3. Click on Code Style
  4. Select Joomla from the Scheme select box

PhpStorm / Alternative Method[edit]

NOTE: This method is outdated, but it might be useful if you are looking for a different integration. It also demonstrates the use of external tools in PhpStorm - so it shouldn't be deleted.

The Code Sniffer can also be integrated easily as an external tool. PhpStorm will display the output in the console, including click-able links containing line and column numbers to the files that contain errors.

  • Click on "Settings" and search for "External tools"
  • Click "Add..."
  • Choose a "Name", "Group" and "Description".
  • Click "Output Filters"
    • Click "Add...", Choose a name and enter under "Regular expression to match output" the value: $FILE_PATH$:$LINE$:$COLUMN$
  • "Program": Search for the phpcs executable on your system. You have to set the path to the phpcs.bat from the installed PHP_CodeSniffer PEAR package
    • For Unix based systems, the path is something like /usr/bin/phpcs
    • In XAMPP (windows), you can find the file in the PHP root folder (e.g. C:\xampp\php\phpcs.bat)
  • "Parameters":
    • --standard=<path/to/joomla-platform>/build/phpcs/Joomla The path to the Joomla! coding standards.
    • --report=emacs The will generate a simple list containing links to the error files
    • Optionally you may want to specify -p for "progress" or -n for "errors only".
    • The last parameter has to be $FilePath$ specifying the file or folder you want to sniff.

A typical "Parameters" line on a Linux system might look like this:

-np --standard=/home/elkuku/libs/joomla/build/phpcs/Joomla --report=emacs $FilePath$

You may now right click any file or folder and choose the sniffer from the context menu or add a new tool bar button with a nice Joomla! logo Icon-16-joomla.png.

Netbeans[edit]

Netbeans has the sniffer functionality integrated into the core system.

  1. Start your Netbeans IDE
  2. Open Tools  Options  PHP  Code Analysis  Code Sniffer
  3. You have to set the path to phpcs.bat from the installed PHP_CodeSniffer PEAR package
    • For Unix based systems the path is something like /usr/bin/phpcs
    • In XAMPP (windows) you can find the file in the PHP root folder (e.g. C:\xampp\php\phpcs.bat)
  4. As "Default Standard," choose "Joomla" to use the Joomla! standard
  5. Now you can click OK to start sniffing
  6. Open from the top menu Source  Inspect
  7. Enjoy

Eclipse[edit]

1) Eclipse PTI

Installation is a breeze and follows the usual pattern:

  1. Help  Install New Software
  2. Work with: Fill in one of the update site URLs found here: http://www.phpsrc.org/eclipse/pti/
  3. Select the desired tools
  4. Restart Eclipse.
2) Eclipse PTI settings

You are now able to sniff for code violations against common standards like PEAR or Zend etc.

To sniff against your own standards, specify their location and activate them:

  1. Window  Preferences
  2. PHP Tools  PHP CodeSniffer

Happy sniffing.

Geany[edit]

  • Open a PHP file. (Otherwise the build menu is not accessible.)
  • On the top menu, select Build->Set Build Commands.
  • Select the second field and name it as you wish. Enter this code in the Command: phpcs --standard=Joomla "%f" | sed -e 's/^/%f |/' | egrep 'WARNING|ERROR'
  • Enter this code in the Error Regular Expression field: (.+) [|]\s+([0-9]+)
  • Select OK.
  • If the Message Window is not open, display it by selecting it in the top View menu.
  • When viewing any PHP file, press F9 to see the errors found.

Atom[edit]

  • Install phpcs and the Joomla standards as described above.
  • In Atom  Preferences  Install install linter-phpcs and all its requirements.
  • In Atom  Preferences  Packages  linter-phpcs  Settings adjust
    • Executable Path to the path of your phpcs
    • Code Standard Or Config File: Joomla
    • Tab Width: 4

References[edit]