I second this. though i found the github code for code_check and
autotest. i think having 1 for Php_codesniffer would be a very good
idea to increase cake usage as well.
Braindead wrote:
> Hi Achilleas,
>
> you are right that CodeSniffer validates your code to make sure that
> it follows certain c
Hi Achilleas,
you are right that CodeSniffer validates your code to make sure that
it follows certain conventions. It is possible to define a validation
set that reflects CakePHPs conventions. If your code doesn't follow
these conventions CodeSniffer gives you a warning and you have the
possibilit
Hi Markus,
I am not very familiar with codesniffer, but from what I make up from
it's project page it is somewhat similar to the w3 xhtml, css, etc
validation tools. Correct me if I am wrong.
What is often the case with these tools is that they should be used as
guidelines more than strict rules.
I use this plugin with NetBeans, too. Which coding standard you want
to use is just a matter of taste. In every case you have to make the
standard follow Cake conventions and this is my problem. Is there
really no one who uses CodeSniffer in a Cake project?
Check out the new CakePHP Questions site
Hi,
I want to use coding standards with my cake app too.
The default coding standard is pear. You can change default standard
see the Code Sniffer doc.
If you use netbeans there's a plugin to check your code.
http://www.amaxus.com/cms-blog/coding-standards-netbeans-php-codesniffer
I don't find a c
