Hi,
I've noticed some issues with Drupal coding standards, unused namespace imports, wrong comments, etc.
It would be nice to fix.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | coding-standards-fixes-2979636-6.patch | 44.51 KB | afi13 |
| #3 | coding standerd 11.png | 3.57 MB | riddhi.addweb |
| #2 | coding-standards-fixes-2979636-2.patch | 41.2 KB | afi13 |
Comments
Comment #2
afi13 commentedComment #3
riddhi.addweb commented@afi13, Thanks for solving the standard issues, I verify it with Pareview.sh. I found some file changes are missing to work upon. Can you please do the needful for the same. PFA in that I mentioned the missing files.
Comment #4
afi13 commentedComment #5
afi13 commentedComment #6
afi13 commentedREADME file is update also and added all required sections.
Comment #7
john.oltman commented@afi13 appreciate the patch. The module has a README.txt and not a README.md, would you be able to post your entire README.md file as a file attachment so I can incorporate that into the commit. Thank you!
Comment #8
dwwThanks for this patch! It's fixing a lot of problems. However, it's introducing some of its own. ;) I haven't super closely reviewed everything in here, but here's what I saw on a first read:
A)
Nope, we don't want
array()syntax. This should be:return ['my_module' => ['my_token' => 'my_value']];B)
If we're going to change this, we should simplify it to this:
C) I know 80 character limit and all that, but I really don't think this helps readability of this logic:
D) Ditto here:
If you really must split this line, let's do it like so:
E) Typo in the "fixed" version:
F) 80 character rule definitely does *not* apply to annotation comments. That's all magic, and you don't want newlines in there.
Cheers,
-Derek
Comment #9
afi13 commentedComment #10
john.oltman commentedComment #12
john.oltman commentedComment #13
john.oltman commentedComment #15
avpaderno