On Thu, 8 Sep 2016, at 09:07 AM, Lester Caine wrote: > I've just been through an exercise to give PHP_CodeSniffer a go on my > code base. I've not worried too much about that in the past since > Eclipse in general flags style problems as well as simple errors. This > is a package that SUSE does not support, so the current install path is > just PEAR. I don't see packages like this as a library that my sites > use. It is a stand alone tool ( and a command line one at that :) ) so > how would loading that be managed if PEAR is not available?
PHP_CodeSniffer is already compatible with Composer, and Composer has the ability to specify dependencies, and dependencies intended for development. After running composer install you can execute `vendor/bin/phpcs`, and if you were working collaboratively, collaborators would all have the same toolset that you have. -- Daniel Morris dan...@honestempire.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
