3. WORKING FOR
ResearchGate gives science back to the people who make it happen.
We help researchers build reputation and accelerate scientific
progress.
On their terms.
9. THE TOOLS
PHP MESSDETECTOR
Complexity, long term maintainability, keeps you honest when
designing
PHP CODE SNIFFER
Code formatting, simple coding errors, helps you stay consistent in a
team
10. PURPOSE (IMHO)
PHPMD is for naming, size, complexity and all the hard to change
things
PHPCS is for whitespace and all the things that are easy to fix
11. HOW TO MAKE USE OF THEM
Configure rules that match the way you are working!
It's easier than it feels!
12. WHAT ABOUT STANDARDS?
PHPMD: Use all the rules, they are reasonable. Configure them later
PHPCS: Use PSR2. Replace things if they don't work for your team
14. DEMO
Let's create ruleset files for both of the tools :)
http://edorian.github.io/php-coding-standard-generator/#phpmd
15. COMMANDS USED
Use most of PHPMDs rules:
Use your custom ruleset:
Use PSR2 with PHPCS:
Use your own PHPCS rules:
phpmd source text codesize,unusedcode,naming,design
phpmd source text phpmd.xml
phpcs --standard=PSR2 source/
phpcs --standard=phpcs.xml source/
16. CONTINUOUS INTEGRATION
Real world usage along a projects lifecylce
Pretty graphs in Jenkins!
Fail your travis ci build on phpcs errors?
Fail your travis ci build on phpmd errors???
