Start to separate coding standards and best practices to their own rulesets #1475
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Base ruleset is
WordPress-Core
.Thinking:
Have a look at the files. I'll go through WordPress-Extra and separate the extras / overrides from that onto either of these. Not sure how to handle the layered approach to be honest.
Would a WordPress-Extra-CodingStyle and WordPress-Extra-BestPractices make sense that just imported the previous ones?
Won't that fragment the rulesets?