Upgrade PHPCS standards and fix issues, excluding ExceptionNotEscaped. #8942
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.
Summary
Addresses issue:
Relevant technical choices
I updated the suggested packages and their dependencies, then worked through many new fixes and addressed them using
lint-fix
and manually.The only rule that I suggest we address in a follow up issue is
WordPress.Security.EscapeOutput.ExceptionNotEscaped
, which I've disabled here for now. There are many examples where we return variables in our error response strings. As mentioned in this thread, the security impact here is for uncaught/handled errors for:In our usage we may be able to skip many of these where the errors are part of REST endpoints where the response won't be rendered in the users site/plugin dashboard. Other core plugin exceptions should perhaps be escaped incase they are left uncaught and could return unescaped html on the plugin dashboard. Generally creating a new ticket will allow us to evaluate the possible impact through the AC/IB process.
Alternatively if we are clear that each error is correctly handled by the plugin we can permanently disable this rule.
PR Author Checklist
Do not alter or remove anything below. The following sections will be managed by moderators only.
Code Reviewer Checklist
Merge Reviewer Checklist