goatherd/phpcs_installer

Composer-installer for phpcs standards.

phpcs installer

deprecated in most cases you should be fine with a setup like descriped by this pull request.

Please note that this package is no longer maintained as the need to patch standards into the CodeSniffer path structure does no longer exist.

phpcs_installer's Issues

Support for the 2.* release of php_codesniffer

As of the 5th of February, a new 2.0.0 version of PHP_CodeSniffer is in the works: http://www.squizlabs.com/php-codesniffer/2.0.0a1-released

In addition to being able to find problems in code, this branch also allows you to write code to fix the problems. We're using this in the Drupal project to write 7 to 8 code upgrade routines, and have an open issue to switch to Composer to put everything together, https://drupal.org/node/2194285 but it's dependent on this project supporting the new branch, from what I understand.

cleanup and adjust documentation for 1.2 tag

• alias master branch as 1.x-dev
• add documentation for custom path
• remove incomplete root-script
• document root-script alternative
• proof-read docs

When done tag as 1.2.1 (no behaviour changed, no features added).

Set path to codesniffer standards

May want to use a different vendor or package to provide codesniffer.

Test updateability

It is not yet well understood how (archive based) composer updates to phpcs do effect nested standards.

use composer plugin api

https://getcomposer.org/doc/articles/plugins.md

document limitations and usage in more detail

It should be clear what was tested and should be supported.
Use cases that made this installer favorable should be better understood and communicated.

It may not be suited as a good practice or universal standard installer.

Feature request: custom standard name

It would be nice to be able to specify the directory name for the standard rather than have it be based on the package name. Maybe something that could be specified in the extra key of the standard's composer.json.