-
Notifications
You must be signed in to change notification settings - Fork 60
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
Show check name in results #380
Conversation
00905ca
to
728aff3
Compare
Looks like PHPUnit tests also need to be adjusted with new |
d7603c2
to
80b51db
Compare
80b51db
to
aa1c4b6
Compare
This is an alternative to #376, correct? |
Yes. |
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.
Thanks @ernilambar for the PR! Left some feedback and questions for consideration.
c7d2170
to
09587a7
Compare
09587a7
to
2f1244b
Compare
PR updated. |
If we display the check name/slug in the results like this, we need to be certain it‘s correct and matches the slug used in Default_Check_Repository. This way users can easily exclude the check next time around. But what if someone uses the wp_plugin_check_checks filter to add their custom check where this might not be the case (i.e class name differe heavily from the array key)? IMHO the current solution is not robust enough for this case. |
What if validate slug and class name in Another alternative: |
Closing. We need to explore more robust approach. |
Related to #329
Sample output: