Problem/Motivation
Running php code sniffer shows errors and warnings.
Steps to reproduce
$ phpcs --standard=Drupal,DrupalPractice --extensions=php,module,inc,install,test,profile,theme,css,info,txt,md .
Proposed resolution
Use phpcbf and manual effort to fix.
| Comment | File | Size | Author |
|---|---|---|---|
| #15 | interdiff_9-15.txt | 587 bytes | sourabhjain |
| #15 | 3265732-15.patch | 8.65 KB | sourabhjain |
| #4 | interdiff_2-4.txt | 7.04 KB | victoria-marina |
| #2 | 3265732-2.patch | 7.67 KB | sourabhjain |
Comments
Comment #2
sourabhjainResolved the coding standard issues. Please review it.
Comment #3
papagrande@sourabhjain, thank you for your help.
A few issues remain:
Please remove all commented out
ksm()and other debugging code.I'm also still seeing one phpcs warning:
Comment #4
victoria-marina commentedHere is a patch. Kindly review it.
Comment #5
Guilherme Rabelo commentedI will review it.
Comment #6
Guilherme Rabelo commentedOnly one issue appeared after applying the last patch.
So i just fix that.
Kindly review it.
Comment #7
papagrande@victoria-marina, @guilherme-rabelo, thank you for your help.
This won't work because the eloqua_api_auth_fallback modules isn't always enabled. It's also not good to have circular dependencies between modules.
Perhaps the best solution for now would be to ignore this warning by adding
// phpcs:ignore DrupalPractice.Objects.GlobalDrupal.GlobalDrupalabove the line.Please also name your patches according to https://www.drupal.org/docs/develop/git/using-git-to-contribute-to-drupal/patch-and-merge-request-guidelines#naming-conventions
Comment #8
victoria-marina commentedComment #9
victoria-marina commented@PapaGrande thanks for your reply! Here is a patch following your considerations.
Comment #10
tmaiochi commentedI'll do the review!
Comment #11
tmaiochi commentedThe patch in comment #9 fixed all messages from PHPCS correctly, and following the comment #7. Moving to RTBC!
Comment #12
papagrande@victoria-marina, @tmaiochi, thanks.
One more small nit: add a space before "1".
Have any of you tested the module with the patch applied?
Comment #13
papagrandeComment #14
sourabhjainI will update this.
Comment #15
sourabhjainResolved the issue which is mentioned in #12
Please review.
Comment #17
papagrandeThanks, all.