Closed (fixed)
Project:
Drupal core
Version:
7.x-dev
Component:
documentation
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
19 Feb 2010 at 03:06 UTC
Updated:
19 May 2010 at 07:20 UTC
Jump to comment: Most recent file
Comments
Comment #1
add1sun commentedWow, look at me, I'm just making stuff up! But we should at least have a docblock here, eh?
Comment #2
pasqualle- removed the variable type from @param
- removed trailing spaces
- used descriptions from other functions (I am not sure if it is better)
Comment #4
pasqualle@@ -183,6 +183,15this is the problem with my patch. I just modified the patch file, and forgot that it has more lines than the first patch. So it needs a reroll.Comment #5
add1sun commentedWhen working on other patches Crell pointed out that adding the variable type is desirable now and some examples on http://drupal.org/node/1354 use that, so the variable type needs to go back in.
Comment #6
pasqualleit's amazing how inconsistent Drupal core is.. I do not understand why they did not roll a patch when that handbook page was made..
or roll a patch for: http://drupal.org/project/coder_tough_love
Comment #7
jhodgdonThat's a new standard.
Rolling a single patch to figure out all of the @param and @return types and adding them to Drupal core would have been a HUGE HUGE HUGE task, and the patch would never have gotten reviewed.
Comment #8
jhodgdonAnother comment on the patch in #2: All function headers should start with a verb in 3rd person, such as "Fetches" rather than "Fetch".
Comment #9
add1sun commentedRerolled
Comment #10
jhodgdonLooks good, except shouldn't we say ID rather than id?
Hmm... Also I think maybe we shouldn't call it a $user object, since $user is the global for the currently logged-in user...
How about this wording?
Comment #11
smyleeface commentedFormatting looks good and wording makes sense to me.
Comment #12
webchickw00t for docs! Committed to HEAD. :)