-
Notifications
You must be signed in to change notification settings - Fork 65
Fix new Plugin Check errors #1023
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
Conversation
… and ignore security advisory for that. Run WP 6.8 as our minimum in our E2E tests so Woo can be installed
…ia composer as it breaks PHPCS otherwise
peterwilsoncc
left a comment
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.
This looks good to me with a minor change inline. I will push the change and then merge.
I've verified the changes in includes/Classifai/Features/ContentGeneration.php are removing unused items.
| - Another tag | ||
| - ... | ||
| EOD; | ||
| // phpcs:enable Squiz.PHP.Heredoc.NotAllowed |
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.
Need to reenable all the sniffs. It's easier to do it like this rather than add individually.
(As this is outside the diff, the suggestion isn't displaying correctly.)
| // phpcs:enable |
Description of the Change
A newer version of Plugin Check was recently released and it is now flagging new things. This PR fixes those.
How to test the Change
Nothing really needed here other than ensuring the plugin checks pass
Changelog Entry
Credits
Props @dkotter
Checklist: