Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
18 Nov 2020 at 12:12 UTC
Updated:
21 Jun 2021 at 11:29 UTC
Jump to comment: Most recent
Comments
Comment #2
avpadernoComment #3
mrweiner commentedSome standards violations from phpcs
FILE: /app/web/modules/contrib/sms_esendex/drush/sms_esendex.drush.inc
------------------------------------------------------------------------------
FOUND 3 ERRORS AFFECTING 3 LINES
------------------------------------------------------------------------------
1 | ERROR | [x] The PHP open tag must be followed by exactly one blank line
2 | ERROR | [x] You must use "/**" style comments for a file comment
24 | ERROR | [x] Doc comment short description must end with a full stop
------------------------------------------------------------------------------
PHPCBF CAN FIX THE 3 MARKED SNIFF VIOLATIONS AUTOMATICALLY
------------------------------------------------------------------------------
FILE: /app/web/modules/contrib/sms_esendex/drush/sms_esendex.drush.inc
-----------------------------------------------------------------------
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
-----------------------------------------------------------------------
2 | WARNING | There must be no blank line following an inline comment
-----------------------------------------------------------------------
Comment #4
mrweiner commentedSorry, just took a look through https://groups.drupal.org/node/427683 and the above doesn't warrant Needs Work.
Comment #5
avpadernoComment #6
sluc23 commented@mrweiner phpcs errors are fixed now in branch
7.x-1.x-devhttps://git.drupalcode.org/project/sms_esendex/-/tree/7.x-1.x-dev
Comment #7
sluc23 commentedComment #8
avpadernoComment #9
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.
I thank all the dedicated reviewers as well.