Actions

Difference between revisions of "Joomla CodeSniffer"

From Joomla! Documentation

(PHPStorm)
(Installing PHP PSR-0, PSR-1 and PSR-2 Sniff)
(18 intermediate revisions by 2 users not shown)
Line 91: Line 91:
 
=== PHPStorm ===
 
=== PHPStorm ===
  
==== PHPStorm 4.x ====
+
==== PHPStorm ====
CodeSniffer is supported out of the box, just go to settings, and under "Inspections" you will see Joomla (*)
+
[[Image:PhpStorm4CodeSniffer.png|left|thumb|200px|1) PHPStorm  4.x CodeSniffer]]
 +
<div style="clear: both"></div>
  
(*) if you are using Xampp and did unpack Joomla CodeSniffer rules under \xampp\php\PEAR\PHP\CodeSniffer\Standards\Joomla
+
CodeSniffer is supported out of the box in PHPStorm, just go to settings, and under "Inspections" you will see the list of Sniff you have installed.
  
[[File:PhpStorm4CodeSniffer.png]]
+
See: The [http://blog.jetbrains.com/webide/2012/03/checking-your-code-with-php-code-sniffer-in-phpstorm-4-0/ phpStorm Blog])
  
==== PHPStorm  3.x ====
+
===== Installing Joomla Sniff =====
There is currently no plugin available, but the CodeSniffer can be integrated easily as an external tool (phpStorm will support CodeSniffer in Version 4.x. It can be used already in the EAP / Beta: [http://blog.jetbrains.com/webide/2012/03/checking-your-code-with-php-code-sniffer-in-phpstorm-4-0/ phpStorm Blog]). PHPStorm will display the output in the console, including clickable links containing line and column numbers to the files that contain errors.
+
 
 +
if you are using Xampp,  
 +
# unpack Joomla CodeSniffer rules under \xampp\php\PEAR\PHP\CodeSniffer\Standards\Joomla
 +
# Go to Settings (CTRL-ALT-S) and search for "PHP Code Sniffer Validation", click the button Validate to force reload of rules from disk
 +
# Joomla is available in the list
 +
 
 +
 
 +
==== PHP PSR-0, PSR-1 and PSR-2 ====
 +
* https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-0.md
 +
* https://github.com/pmjones/fig-standards/blob/psr-1-style-guide/proposed/PSR-1-basic.md
 +
* https://github.com/pmjones/fig-standards/blob/psr-1-style-guide/proposed/PSR-2-advanced.md
 +
 
 +
===== Installing PHP PSR-0, PSR-1 and PSR-2 Sniff =====
 +
 
 +
A CodeSniffer sniff to check against the PSR-x Coding Standard
 +
 
 +
Download files at
 +
* https://github.com/squizlabs/PHP_CodeSniffer/tree/master/CodeSniffer/Standards
 +
 
 +
if you are using Xampp,
 +
# unpack PSR-1 CodeSniffer rules under \xampp\php\PEAR\PHP\CodeSniffer\Standards\PSR (SPR or any directory will work)
 +
# Go to Settings (CTRL-ALT-S) and search for "PHP Code Sniffer Validation", click the button Validate to force reload of rules from disk
 +
# PSR is available in the list
 +
 
 +
==== PHPStorm  3.x / Alternative method ====
 +
'''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.</note>
 +
 
 +
<del>There is currently no plugin available</del> The CodeSniffer can also be integrated easily as an external tool. PHPStorm will display the output in the console, including clickable links containing line and column numbers to the files that contain errors.
  
 
* Click on "Settings" and search for "External tools"
 
* Click on "Settings" and search for "External tools"

Revision as of 13:36, 23 November 2012

(This page needs expanded installation instructions, especially for Windows-based systems.)

Contents

A Nose For Joomla

This is a custom coding standard for the PHP CodeSniffer that attempts to codify and enforce the Joomla coding standards.

Why?

- Coherent and consisting 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, the sometimes developers will reformat the code to suit themselves. This causes a wide range of changes in the code repository, and if there is a later problem, a significant change could be lost in the chaff produced by a diff.

Installation

First of all you have to install the PHP CodeSniffer. This set of files is intended to work with phpcs version 1.3, so behavior with any other version is undefined. One way to do this is to start the console (cmd.exe in windows environments) and type:

pear install PHP_CodeSniffer-1.3.2

Pear will handle the whole installation by itself.

Then download and unzip the Joomla! CodeSniffer and copy the contents of it into /path/to/PHP_CodeSniffer/Standards/Joomla.

In Unix systems this path is usualy /usr/lib/php/PHP/PHP_CodeSniffer/Standards/Joomla but this varies from system to system. Windows based system with XAMPP have the following path: PATH_TO_XAMMP\php\PEAR\PHP\CodeSniffer\Standards (for example: C:\xampp\php\PEAR\PHP\CodeSniffer\Standards)

Use

pear config-get php_dir

to find out where the PEAR directory is on your system, then add "/PHP/PHP_CodeSniffer/Standards" to it.

Usage

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: [1]

IDE integration

While everybody loves the console as 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 plugin available for eclipse and netbeans that integrates the CodeSniffer in our favorite IDE, so any coding standard violations are shown like "normal" errors.

Netbeans

For netbeans you have to install the sniffer plugin first. You can download the plugin here.

  1. Start your netbeans IDE
  2. Open Tools => Plugins => Downloaded and press Add Plugin
  3. Choose the loaded nbm file and confirm the installation
  4. Now there is a new tab in Tools => Options => PHP called "PHPCodeSniffer"
  5. 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)
  6. As "standard" type "Joomla" to use the Joomla! standard
  7. now you can click test Settings to check the settings and finish the installation by pressing Ok
  8. Open he task window (Window => Tasks) to sniff your code.
  9. Most time it is a good idea to filter the task (show only in edited file or create an own filter which displays only sniff errors)

Eclipse

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, all you have to do is specify their location and activate them (see screen shot 2)

  1. Window => Preferences
  2. PHP Tools => PHP CodeSniffer

Happy sniffing

PHPStorm

PHPStorm

1) PHPStorm 4.x CodeSniffer

CodeSniffer is supported out of the box in PHPStorm, just go to settings, and under "Inspections" you will see the list of Sniff you have installed.

See: The phpStorm Blog)

Installing Joomla Sniff

if you are using Xampp,

  1. unpack Joomla CodeSniffer rules under \xampp\php\PEAR\PHP\CodeSniffer\Standards\Joomla
  2. Go to Settings (CTRL-ALT-S) and search for "PHP Code Sniffer Validation", click the button Validate to force reload of rules from disk
  3. Joomla is available in the list


PHP PSR-0, PSR-1 and PSR-2

Installing PHP PSR-0, PSR-1 and PSR-2 Sniff

A CodeSniffer sniff to check against the PSR-x Coding Standard

Download files at

if you are using Xampp,

  1. unpack PSR-1 CodeSniffer rules under \xampp\php\PEAR\PHP\CodeSniffer\Standards\PSR (SPR or any directory will work)
  2. Go to Settings (CTRL-ALT-S) and search for "PHP Code Sniffer Validation", click the button Validate to force reload of rules from disk
  3. PSR is available in the list

PHPStorm 3.x / Alternative method

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.</note>

There is currently no plugin available The CodeSniffer can also be integrated easily as an external tool. PHPStorm will display the output in the console, including clickable 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)
  • "Paramaters":
    • --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
    • Optional 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 toolbar button with a nice Joomla! logo Icon-16-joomla.png.

References