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

Question about PluginCheck.CodeAnalysis.ImageFunctions.NonEnqueuedImage sniff #831

Open
jcvignoli opened this issue Dec 13, 2024 · 0 comments
Labels
[Team] Performance Issues owned by Performance Team

Comments

@jcvignoli
Copy link

jcvignoli commented Dec 13, 2024

Hi there,

I don't understand the point of this new PluginCheck.CodeAnalysis.ImageFunctions.NonEnqueuedImage as implemented there:

plugin-check/phpcs-sniffs/PluginCheck/Sniffs/CodeAnalysis/ImageFunctionsSniff.php

which results in Images should be added using wp_get_attachment_image() or similar functions

For many of the WP plugins makers , we add images in the WP admin backoffice. Those images are not uploaded to WP gallery, but rather static files called the good old way with an . There is no way to bypass the regex, which will detect any in the plugin.

It is my understanding you're going to change it a warning, as discussed here #757 but I'm questionning even such a warning. To my understanding, even a warning is not appropriate for plugins makers.

Even if the aim is undertandable, in practice it doesn't make sense to me.

@ernilambar ernilambar added the [Team] Performance Issues owned by Performance Team label Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Team] Performance Issues owned by Performance Team
Projects
None yet
Development

No branches or pull requests

2 participants