Closed (fixed)
Project:
Coder Tough Love
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
5 Dec 2011 at 15:21 UTC
Updated:
19 Jan 2012 at 23:00 UTC
Jump to comment: Most recent file
Comments
Comment #0.0
xjmUpdated issue summary.
Comment #0.1
xjmUpdated issue summary.
Comment #1
xjmAttached patch simply removes this warning.
Comment #2
danepowell commented+1... will test this out and report back
Comment #3
danepowell commentedPatch in #1 doesn't apply cleanly to HEAD- here's an updated patch.
Comment #4
danepowell commentedMy bad... please ignore #3. The patch failed to apply due to a misconfiguration.
However, I found another very similar bug- 'object' is not recognized as a valid Doxygen return type. The attached patch adds 'object' to the valid return types.
Since technically any sort of class can now be defined as a return type, should this rule be changed in a more general way? Maybe to look for spaces that would indicate a description rather than a return type?
Comment #5
xjmRe: #4: Please open a separate issue for the other bug. Thanks!
Comment #6
hass commented#1390034: @param and @return syntax does not indicate the data type.
Comment #7
xjmCommitted to 6.x-1.x and 7.x-1.x:
http://drupal.org/commitlog/commit/7948/94457fbac8b1c80e92487b0c6823abb4...
http://drupalcode.org/project/coder_tough_love.git/commit/fd7f9f7
Let's fix the additional issue from #4 separately in #1390040: several datatypes are not matched in API docs, triggering '@param and @return descriptions begin indented on the next line'.
Comment #8.0
(not verified) commentedUpdated issue summary.