Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The ParamCommentFullStop error should be automatically fixable. I will try to create a patch to allow this.
Comment | File | Size | Author |
---|---|---|---|
#4 | interdiff-2721239-2-4.txt | 2.15 KB | anoopjohn |
#4 | coder-fix-paramcommentfullstop-2721239-4.patch | 1.84 KB | anoopjohn |
Comments
Comment #2
anoopjohn CreditAttribution: anoopjohn at Zyxware Technologies commentedPlease find a patch that does this. Please review and let me know if there are issues.
Comment #3
klausilet's not modify bad.php. It it used for legacy purposes, but anything that should produce an error/warning should be put in the sniff specific unit test. In this case FunctionCommentUnitTest.inc
Comment #4
anoopjohn CreditAttribution: anoopjohn at Zyxware Technologies commentedThanks for the review and inputs. I have updated the patch.
I have also started a documentation page on how to contribute to coder.
https://www.drupal.org/node/2731617
It would be good to document this so that new contributors will be able to contribute to coder more easily without having to eat into the time of the maintainers (which I seem to be doing well now - thanks for all the patient guidance).
Comment #5
anoopjohn CreditAttribution: anoopjohn at Zyxware Technologies commentedComment #7
klausiRan phpcbf --standard=PHPCS one more time on the sniff file and committed the result, thanks!
Comment #8
anoopjohn CreditAttribution: anoopjohn at Zyxware Technologies commentedGreat. Thanks.