This module overrides image templates and provides preprocessing to standardize use of the HTML <picture> tag, as opposed to standalone <img> tags. It steps into preprocessing late in the process, so that code and developers who assume/are used to having just an <img> tag still have standard markup to work with. Attributes are parceled out to either the <picture> or <img> tag using a configurable + partially hardcoded list of attributes that should go on the <img> tag, with everything left over going to the <picture>.
It also has some optional integrations with other modules such as WebP (automatic webp source for non-responsive images) and SVG Image Field (also wrapping those <img> tags as well).
Comments
Comment #2
avpadernoThank you for applying!
Please read Review process for security advisory coverage: What to expect for more details and Security advisory coverage application checklist to understand what reviewers look for. Tips for ensuring a smooth review gives some hints for a smother review.
The important notes are the following.
phpcs --standard=Drupal,DrupalPracticeon the project, which alone fixes most of what reviewers would report.To the reviewers
Please read How to review security advisory coverage applications, What to cover in an application review, and Drupal.org security advisory coverage application workflow.
Reviewers only describe what needs to be changed; they don't provide patches to fix what reported in a review.
Comment #3
vishal.kadam1. Fix PHPCS issues. You can use the PHPCS tool for checking and resolving issues.
2. FILE: picture_everywhere.info.yml
- remove commented code
- Drupal 10 requires at least PHP 8.1. PHP 8.1.6 is recommended. PHP version requirement needs to be updated accordingly.
php: 8.0Comment #4
vishal.kadamComment #5
bvoynickChanges are committed to the 1.0.x branch.
1. Lines over 80: Okay, I've disabled the custom line limits in the module's phpcs.xml.dist, and linted for the resulting column 80 issues.
I'm not seeing the other errors shown in #3. Make sure you're using the latest drupal/coder, version 8.3.17 or newer. For instance, #3123282 recently changed docblock standards so that an @var tag is not required if the property already has a type declaration in PHP itself.
2. Commented properties: okay, removed.
PHP requirement: the module supports Drupal 9.4.x or later. (This can be checked in the core_version_requirement property.) Drupal 9.x itself only outright requires PHP 7.3, though I think the messaging lately is that at least 8.0 is "strong recommended" for 9's latest minor versions. If and when the module drops Drupal 9 support the PHP version requirement could indeed be increased, or possibly removed.
Comment #6
vishal.kadam@bvoynick,
I have reviewed the changes, and they look fine to me.
Let’s wait for other reviewers to take a look and if everything goes fine, you will get the role.
Thanks
Comment #7
avpadernoThe second parameter passed to
setErrorByName()needs to be a translatable string.Comment #8
avpadernoThank you for your contribution! I am going to update your account.
These are some recommended readings to help with excellent maintainership:
You can find more contributors chatting on the Slack #contribute channel. So, come hang out and stay involved.
Thank you, also, for your patience with the review process.
Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
I thank all the reviewers.
Comment #9
bvoynickThanks folks!
And thanks for pointing out that untranslated string.
Comment #11
avpadernoComment #12
avpaderno