Hello
Is there any plan to use a PHP_CodeSniffer ruleset.xml file to define the fixers to apply ?
Zakarisz
All 6 comments
this is not PHP_CodeSniffer and we won't use it's ruleset.xml file.
If you want to create your own configuration please use .php_cs file as mentioned in readme.
keradus
on 10 Feb 2015
The readme says
_If you are already using PHP_CodeSniffer to identify coding standards problems in your code, you know that fixing them by hand is tedious, especially on large projects. This tool does the job for you._
IMHO, you should not mention this tool if you don't want to work with.
Zakarisz
on 10 Feb 2015
And this say nothing about using two tools together ;)
keradus
on 10 Feb 2015
"If you use PHP_CodeSniffer, you will find something to fix in your code. It is tedious to fix it by hand so we did a tool to do it automatically, but don't use both together".
Funny philosophy !
Zakarisz
on 10 Feb 2015
Both tools can be used together, although there would be no real benefit to that. The description you provided, just explains that the other tool only points out the errors and you had to fix them by hand (in previous versions), this tool fixes them right away. So it is only mentioned to explain the value of php-cs-fixer. As said you can use a configuration file to define which rules to apply, just not the .xml file used by the other tool.
ceeram
on 10 Feb 2015
everything is explained, closing
keradus
on 10 Feb 2015
Related issues
UksusoFF
路
3Comments
sennewood
路
3Comments
CMalvika
路
3Comments
EvgenyOrekhov
路
3Comments
aidantwoods
路
3Comments
Most helpful comment
The readme says
_If you are already using PHP_CodeSniffer to identify coding standards problems in your code, you know that fixing them by hand is tedious, especially on large projects. This tool does the job for you._
IMHO, you should not mention this tool if you don't want to work with.