Rename phpcs.xml to ruleset.xml

[jamesmehorter]

In order for phpcodesniffer-composer-installer to automatically install rulesets loaded via Composer, the ruleset file must be named ruleset.xml. This seems to be completely undocumented anywhere—but while named phpcs.xml, phpcodesniffer-composer-installer does not automatically install the ruleset.

With this change, after installing with Composer, you can immediately see phpcs-laravel listed as an installed ruleset with phpcs -i. And likewise, you can then use it with: phpcs --standard=phpcs-laravel.

[jamesmehorter]

The closest documentation I could find is here https://github.com/Dealerdirect/phpcodesniffer-composer-installer#developing-coding-standards and here https://github.com/squizlabs/PHP_CodeSniffer/wiki/Coding-Standard-Tutorial

They have you create a ruleset as ruleset.xml, but it's not mentioned that this is a hard requirement.

[jamesmehorter]

Using this method: https://github.com/Dealerdirect/phpcodesniffer-composer-installer#calling-the-plugin-directly

Before the name change:

→ composer run-script install-codestandards              
> Dealerdirect\Composer\Plugin\Installers\PHPCodeSniffer\Plugin::run
PHP CodeSniffer Config installed_paths set to ../../automattic/vipwpcs,../../sirbrillig/phpcs-import-detection,../../sirbrillig/phpcs-variable-analysis,../../wp-coding-standards/wpcs

After the name change

→ composer run-script install-codestandards
> Dealerdirect\Composer\Plugin\Installers\PHPCodeSniffer\Plugin::run
PHP CodeSniffer Config installed_paths set to ../../sirbrillig/phpcs-import-detection,../../sirbrillig/phpcs-variable-analysis,../../wp-coding-standards/wpcs,../../emielmolenaar,../../automattic/vipwpcs

Note the addition of ../../emielmolenaar

[emielmolenaar]

Thank you @jamesmehorter !