Skip to content
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

Errors in Performance Lab Plugin Detected by Plugin Checker #787

Closed
mukeshpanchal27 opened this issue Jul 20, 2023 · 3 comments · Fixed by #788
Closed

Errors in Performance Lab Plugin Detected by Plugin Checker #787

mukeshpanchal27 opened this issue Jul 20, 2023 · 3 comments · Fixed by #788
Assignees
Labels
Infrastructure Issues for the overall performance plugin infrastructure Performance Lab Plugin Issue relates to work in the Performance Lab Plugin only [Type] Bug An existing feature is broken

Comments

@mukeshpanchal27
Copy link
Member

Bug Description

When i check the Performance Lab plugin in Plugin Checker tool it shows errors that we have to fix in upcoming release.

When running the Performance Lab plugin through the Plugin Checker tool, we discovered that several errors were flagged. These issues need to be addressed and fixed in the upcoming release.

Screenshots

Screenshot 2023-07-20 at 12 04 16 PM
@mukeshpanchal27 mukeshpanchal27 added [Type] Bug An existing feature is broken Needs Dev Anything that requires development (e.g. a pull request) [Focus] Server Response Time Issues related to the Server Response Time priority focus area Performance Lab Plugin Issue relates to work in the Performance Lab Plugin only labels Jul 20, 2023
@mukeshpanchal27
Copy link
Member Author

cc. @eclarke1 @felixarntz @joemcgill

@felixarntz
Copy link
Member

Thanks @mukeshpanchal27!

Regarding the hidden files error, we can probably just remove the .gitkeep file? Otherwise we could exclude it so that it doesn't make it to .org, but I'd argue we don't even need that file anymore.

For the other errors, they make sense, but there seems to be an issue with our tooling here, since our PHP linting workflow should have caught this long ago?

I just took a closer look, and it looks like the issue is that the ./server-timing directory is not part of our phpcs.xml.dist config, looks like we failed to update that. phpstan.neon.dist looks like it's complete though, so we should probably make sure to align the phpcs.xml.dist list of directories and files. When we address those issues, we'll also have addresses those violations that the plugin checker found.

@felixarntz felixarntz added Infrastructure Issues for the overall performance plugin infrastructure and removed [Focus] Server Response Time Issues related to the Server Response Time priority focus area labels Jul 20, 2023
@felixarntz felixarntz added this to the PL Plugin 2.6.0 milestone Jul 20, 2023
@mukeshpanchal27 mukeshpanchal27 removed the Needs Dev Anything that requires development (e.g. a pull request) label Jul 21, 2023
@mukeshpanchal27 mukeshpanchal27 self-assigned this Jul 21, 2023
@swissspidy
Copy link
Member

swissspidy commented Jul 21, 2023

WordPress core itself trusts translations, which is why you don't see __() calls being escaped anywhere. Many plugins do the same. We should consider updating the Plugin Checker to either not flag translation calls or at least make them warnings. It really adds a lot of noise for something that is not even considered an issue by the plugin review team.

Just imagine how many errors/warnings bigger plugins will get because of that. They will be immediately scared off from using the Plugin Checker because it's just too much to handle.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Infrastructure Issues for the overall performance plugin infrastructure Performance Lab Plugin Issue relates to work in the Performance Lab Plugin only [Type] Bug An existing feature is broken
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants