Automated project review reported several errors that we should be able to fix without too much trouble, since it's mostly coding standards errors (spaces missing, wrong indent, missing empty lines, etc...).
Let's try to bring back module's code in compliance with coding standards and fix all validation errors.
There shouldn't be any change of code, other than the ones recommended by the coding standards PAReview.
Additionally, I assume these changes could also be back-ported on other branches: 6.x-1.x PAReview report, 5.x-1.x PAReview report
Please let me know if you would have any questions, objections, comments, suggestions, recommendations or concerns on any aspects of this issue, I would be glad to provide more information or explain in more details.
Any questions, feedback, testing, changes, recommendations would be highly appreciated.
Thanks to all in advance.
Comments
Comment #1
DYdave CreditAttribution: DYdave commentedQuick follow-up on this issue:
PAReview is not prompting any errors anymore for all branches:
For all these versions, I didn't do any complicated changes, just fixed the errors as indicated by the reports: wrong spaces, break down too long inline comments, standardize Doc comments blocks, add full stops at end of lines of inline comments, etc....
I have tested a little bit and everything seem to work as expected, but I would greatly appreciate if you could let me know if anybody encounters any issue with the latest commits related with coding standards, I would surely try doing a quick fix as soon as possible.
Please let me know if you would have any questions, comments or issues regarding any of the commits or changes requested in this ticket, I would be glad to provide more information or explain in more details.
Thanks to all in advance for your feedback, testing and reviews.
Cheers!
Comment #3
DYdave CreditAttribution: DYdave commentedTo prepare for new releases, quick checks of the coding standards on pareview.sh revealed the following minor errors:
For reroute_email-7.x-1.x
For reroute_email-6.x-1.x
I went ahead, modified the code as suggested and committed the changes against reroute_email's 7.x-1.x branch at 19582f8 and 6.x-1.x branch at bab9042.
Feel free to let me know if you would have any further comments, feedback, questions, issues, objections, suggestions or concerns on any of the latest code changes or this ticket in general, I would be glad to provide more information or explain in more details.
Thanks in advance to everyone for your testing, reviews, reporting and feedback.
Cheers!