-
Notifications
You must be signed in to change notification settings - Fork 848
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
install phpcs via composer #608
install phpcs via composer #608
Conversation
I fixed the oversight of setting the correct path to the WP coding standards. |
@jeremyfelt please add |
Thanks @cfoellmann!
|
/cc @westonruter for feedback too 😄 |
/srv/www/phpcs/scripts/phpcs --config-set installed_paths ./CodeSniffer/Standards/WordPress/ | ||
/srv/www/phpcs/scripts/phpcs --config-set default_standard WordPress-Core | ||
/srv/www/phpcs/scripts/phpcs -i | ||
sudo /srv/www/phpcs/scripts/phpcs --config-set installed_paths /srv/www/phpcs-wordpress/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This absolute path will break PHPCS when invoked from outside of Vagrant. This is why a relative path is used currently.
The path to the WPCS shouldn't be changed. |
@cfoellmann do you want to address the path naming and update the PR accordingly? It seems like this would help as long as we're consistent with the location. |
I think we need to regroup on this in a new pull request. I've opened issue #922 to describe the intent here. Thanks for the work on this @cfoellmann. :) |
phpcs needs to be installed via composer to reduce the provision process significantly. My last
vagrant provision
took 7039 seconds! mostly due to git clones.