-
-
Notifications
You must be signed in to change notification settings - Fork 170
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
Updated to PHP CodeSniffer 3 #151
Conversation
Awesome job! I'm amazed you think about future compatibility in such level. |
Let me know if you need any help. |
Showcase PR with CodeSniffer upgrade 2.x => 3.x: https://github.com/hostnet/phpcs-tool/pull/16/files |
Hey, I just wanted to ask. I depend with few packages of mine on this, using awesome helpers in it + CodeSniffer 3.0. Among 2 from Symplify, also https://github.com/object-calisthenics/phpcs-calisthenics-rules This is the last unupdated-package to get to stable release, that I'd like to sync with Symfony 3.3 release (in ~10 days). I'd like to know, when do you plan to merge and release CodeSniffer 3.0 version. So I could decide, if I should wait or if I should copy-paste those helpers for now and update them to CodeSniffer 3.0. Thank you |
CodeSniffer in versions |
@VasekPurchart Thanks for linking this. I hope this will be solved ASAP. |
composer.json
Outdated
@@ -9,7 +9,7 @@ | |||
}, | |||
"require": { | |||
"php": "^7.0", | |||
"squizlabs/php_codesniffer": "~2.8.1" | |||
"squizlabs/php_codesniffer": "dev-master" |
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.
Hey, I also need this PR to be merged.
But my custom sniff repository currently depends on "squizlabs/php_codesniffer": "~3.0.0"
.
So I cannot require this branch(also future merged branch).
I suggest the dependency version ~3.0.0
or ^3.0
will be better than dev-master
.
(I say Sorry when you supposed to change this version when PHPCS3.0.1 released.)
Thanks.
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.
Yes, I'll use ^3.0.1 :) I just want to test that there is no other bug in PHPCS.
issues is fixed with phpcs 3.0.1, I think whould possibile use this patch version as minimum requirement. |
No description provided.