-
-
Notifications
You must be signed in to change notification settings - Fork 483
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
Add note regarding WordPress-VIP ruleset #1403
Conversation
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.
- It was originally for [WordPress.com VIP coding requirements] - is this sentence missing the word
intended
or is it just me ? - I'm a bit wary about using the word
soon
in this context all things considering.
Added, and clarified further.
Changed to "in due course". |
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 is no longer used or recommended by the WordPress.com VIP team or their clients.
- Do you meanfor their clients
?
I'm wondering if we shouldn't also remove the VIP
ruleset and the VIP sniffs - <exclude name="WordPress.VIP" />
- from the WordPress
ruleset in this PR.
That way the WPCS side of things would be completely covered by this PR.
Opinions ?
This was meant as a quick workaround whilst the finer points of how such a removal would be done. It was building on Tom's information that the VIP team no longer use it, or recommend it to their clients. I think making an actual change to the characteristics of WPCS, like removing the ruleset, should be its own PR, even if that includes a further change to this readme about its inclusion. |
Just to make sure that we are all on the same page, @jrfnl was suggesting that the I think that makes sense, as otherwise, I'd think a lot of folks would still end up using the VIP sniffs via the |
I can say VIP doesn't recommend the ruleset fullstop, client or not client |
Needs updating as per #1410. See comments at https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/pull/1410/files#r201158500 |
Closing as @GaryJones' textual improvements were implemented in #1410. |
Quick and temporary workaround to reduce the chance of new folks using it:
See #1309.