Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
5 Dec 2022 at 06:10 UTC
Updated:
20 Dec 2022 at 16:59 UTC
Jump to comment: Most recent
Comments
Comment #2
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.
While this application is open, only the user who opened the application can make commits to the project used for the application.
Reviewers only describe what needs to be changed; they don't provide patches to fix what reported in a review.
Comment #3
akshay.singh commentedHi there,
While reviewing your module for best practices and coding standards, I have found several issues.
Comment #4
akshay.singh commentedComment #5
avpadernoThe following seems a false positive. It's probably caused from the fact that the parameter is defined as
array &$variablesinstead of&$variablesas intemplate_preprocess_node().Comment #6
avpadernoAs a side note, check the email used from Git, because that isn't an email associated with your account. That's why the commits aren't associated with your account.
Comment #7
avpadernoWhen I run
phpcs --standard=DrupalPracticeon the 3.x branch, I get the following report.Comment #8
avpadernoRunning the same command for the 2.x branch, I get this report.
Comment #9
ksere commentedHello, thank you! I will take a look at this today and get back to you.
Comment #10
ksere commentedHello!
Seems like my PHPStorm PHPCS was set to 'Drupal' instead of 'DrupalPractice'.
I'll be doing a full review of the standards and I'll push the update through, along with double-checking the email associated.
Should have an update by the end of today!
Comment #11
ksere commentedHello,
I've gone through and cleaned up the errors provided. Mainly the use of $this-t() has been addressed.
I've also removed usage of the
mixedtype across the code. This seems to have been throwing warnings.Changes were brought to both 2.x and 3.x.
Comment #12
akshay.singh commentedHey @ksere,
Still, there are some minor issues left. Please check
Comment #13
akshay.singh commentedComment #14
ksere commentedHello Akshay,
Thank you for reviewing this again. I've gone through and made adjustments for the last fixes.
As for the README.md ones, they do not seem to be accurate as they seem to be applying PHP rules to the
.mdfile. I've ignored most of those for now, but at least made sure the line lengths were below 80 in the README.Comment #15
ksere commentedComment #16
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 #17
avpadernoComment #18
ksere commentedThank you very much Akshay Singh & apaderno!