-
Notifications
You must be signed in to change notification settings - Fork 40
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
Remove BatCache related sniff #492
Comments
+1000000 |
This is important, but changing the class name will create a backwards compatibility break, so that means it needs to be done on a major release. It's possible that all of the VIP clients will have moved over from WordPress.com VIP to VIP Go platform by the time the VIPCS is released, which means that this issue can change to removing this sniff completely, since it's only used in the WordPress-VIP-Minimum ruleset. |
This is now correct, so the BatCache-related sniff can be removed completely now. |
Closing in favour of #613. |
What problem would the enhancement address for VIP?
Words matter, and the current understanding is that whitelist has negative connotations for some people that can be easily avoided by using a different term.BatCache is not used on the current VIP platform, so this sniff is no longer needed.
Describe the solution you'd like
Change class, class properties and any other references to whitelist for something else.Remove the sniff.
Additional context
Apart from the changelog, the only other references seem to be in relation to the BatcacheWhitelistedParams sniff and related test files.The text was updated successfully, but these errors were encountered: