Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
1 May 2022 at 12:37 UTC
Updated:
9 Apr 2025 at 18:06 UTC
Jump to comment: Most recent
Comments
Comment #2
harivenuvComment #3
harivenuvComment #4
harivenuvComment #5
harivenuvComment #6
avpadernoThank you for applying! Reviewers will review the project files, describing what needs to be changed.
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.
To 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.
Comment #7
avpadernomaster isn't a branch name used on drupal.org repositories. 1.0.x-dev is a wrong name for release branches.
A new branch needs to be created, made the default one; once this is done, the other branches can be removed.
Comment #8
harivenuvComment #9
harivenuvHi @apaderno,
Thanks you for the direction, I have changed the development branch name and removed master also made the default branch to dev.
dev branch 1.0.x (default)
Release tag - 1.0.1
Comment #10
Le Vo Trung Hieu commentedHi @harivenuv,
I've review branch 2.0.x again and It's display some issue
1. I use drupal-check
2. I use Drupal Coding Standards
Comment #12
harivenuvComment #13
andrei.vesterliHello @harivenuv
You did a great job and it looks like you considered the case when the field cardinality is unlimited which is good. I've tested it and I like how it works. Also, tried to set a wrong URL and I just got a js console log error, not fatal, which is really good.
Here are some things that require improvements:
Drupalstandardand
DrupalPracticeinstead of declaration of
$themevariable?templates/lottiefiles-player-formatter.html.twigdoes not contain all the used variables. You indicate these:but you use much more:
Regards,
Andrei
Comment #14
andrei.vesterliComment #15
harivenuvHello @andrei.vesterli,
Thanks you for your time to review the module.
$themevariable removedcompose.jsonfile addedPlease review and approve
Thanks,
Hari
Comment #16
harivenuvComment #17
andrei.vesterliHi @harivenuv
Nice! Thx for the quick feedback.
Comment #18
Rajeev cp commentedThanks @harivenuv for this awesome module.
I have tested It in my multilingual website and everything worked as expected.
Comment #19
harivenuvComment #20
harivenuvPlease review
Comment #21
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 IRC #drupal-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.
Thank you to all the reviewers.
Comment #22
harivenuvThank you @apaderno
Comment #24
cmlaraApologies for the noise.
Adding a tracking flag for auditing when modules have been reviewed by the queue only for it to be announced after approval that reviewed code contained a security vulnerability.
SA-CONTRIB-2022-046