-
Notifications
You must be signed in to change notification settings - Fork 56
Implement CS checking based on the WP_CLI_CS ruleset
#117
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
Conversation
jrfnl
left a comment
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.
@wojsmol Thanks for this PR!
I've left a number of comments in-line. Quite a few are just suggestions, but this PR - as is - also introduces a few bugs due to strict comparisons being introduced incorrectly. Please be very careful with those. My remarks will hopefully help you fix them.
Co-Authored-By: wojsmol <wojsmol@wp.pl>
Co-Authored-By: wojsmol <wojsmol@wp.pl>
The code never worked in the first place, but fixing it properly would result in a BC break.
The 1.6 endpoint requires the unsafe `unserialize` method that is flagged by PHPCS. By bumping the version to 1.7, we can replace that with JSON instead.
|
@wojsmol This package was more complicated, so I made a series of general CS tweaks still to get this command more in line with the rest of the packages. I also added a few refactors to get rid of the remaining PHPCS issues. Can you please review the changes I made? |
|
We seem to be having the same issue for trunk here than with the language command: |
|
I'll merge the PR as-is, the remaining failure is unrelated. |
Add a PHPCS ruleset using the new WP_CLI_CS standard.
Fixes #110
Related wp-cli/wp-cli#5179