WordPress ruleset: efficiency fix #1758
Merged
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.
Rulesets are processed top-to-bottom, one rule at the time.
For the
WordPress
ruleset, this means that PHPCS would first load theWordPress-Core
ruleset and process all rules in that file, then read theWordPress-Docs
ruleset and lastly, theWordPress-Extra
ruleset.As the
WordPress-Extra
ruleset includesWordPress-Core
, it would re-process theWordPress-Core
ruleset a second time and then process the additional rules in theExtra
ruleset.This means that in effect, the
WordPress-Core
ruleset is processed twice when using theWordPress
ruleset which is inefficient.By commenting that rule out, we still document that the
WordPress
ruleset includesWordPress-Core
without double processing the ruleset.