Closed (won't fix)
Project:
Coder
Version:
7.x-2.x-dev
Component:
Review/Rules
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
19 Nov 2008 at 07:03 UTC
Updated:
10 Oct 2016 at 11:48 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
stella commentedThe first is a known issue for patches with start with
*/.As for line numbering, the line numbers given aren't the same as the file line numbers, rather they correspond to a line within a given hunk. Each hunk starts with a line something like
@@ -7,6 +7,9 @@. This is because each hunk has to be reviewed separately from each other.Comment #2
stella commentedTry this patch. It should fix both issues:
*or*/.Comment #3
scor commentedthe patch works and fixes the problem with /*/.
however I realize that coder runs a code review on the actual changes of the patch (lines starting with +) and but also on the context of the changes as well. I'm not sure this is a good thing. When I review a patch, I mainly want to see if the code I introduce is valid, and old code issues might confuse me (noise). The coder patch feature should only review the code changes and ignore the older code. my .02 cts.
Comment #4
stella commentedThere's arguments for and against. The main one against your proposal (in my opinion) is that by not reviewing the surrounding lines, we loose context. We could end up reviewing some comment lines and then code lines, without ever actually processing the line that closes the comment block. That would break the reviews - unless we treated each individual set of + lines separately, which I think is too complicated to do for such little gain.
Doug: can you review before I commit it?
Cheers,
Stella
Comment #5
douggreen commentedI suspect this is still a problem?
Comment #6
douggreen commentedComment #7
klausiCoder 7.x is frozen now and will not receive updates. Coder 8.x-2.x can be used to check code for any Drupal version, Coder 8.x-2.x also supports the phpcbf command to automatically fix conding standard errors. Please check if this issue is still relevant and reopen against that version if necessary.