-
Notifications
You must be signed in to change notification settings - Fork 21
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
Resolve some of the plugin check errors and warnings #2772
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #2772 +/- ##
============================================
+ Coverage 66.7% 67.2% +0.6%
- Complexity 0 4677 +4677
============================================
Files 316 480 +164
Lines 4922 19571 +14649
Branches 1204 0 -1204
============================================
+ Hits 3282 13159 +9877
- Misses 1503 6412 +4909
+ Partials 137 0 -137
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
Yes. They also don't show up in the report when you test a release version of the plugin, as we don't bundle the tests folder. |
Changes proposed in this Pull Request:
This PR resolves a substantial amount of the errors and warnings which are identified in the WordPress.org plugin check.
Changes resolve the following errors:
Note
We are ignoring the following errors/warnings:
WordPress.Security.EscapeOutput.ExceptionNotEscaped
- Exceptions can be escaped late when output, not when they are thrown, we have a specific exclusion for this in the phpcs.xml filetrademarked_term
Plugin naming has been done in discussion with trademark ownersWe can address these at a later date if these rules ever become fully required.
Detailed test instructions:
composer install && nvm use && npm run build
Linting php
npm run lint:php
npm run lint:php-tests
Changelog entry