API page: http://api.drupal.org/api/drupal/modules--taxonomy--taxonomy.module/func...
Describe the problem you have found:
The return value can also be an empty array, when no childs are found. This is not described in the Return value. Users with smart IDEs will benefit from these kind of correct informations.
ps: can somebody please set the Drupal Core version to 7.2 (aka current stable) instead of 7.x-dev when reporting issues? Or is that intended?
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | taxonomy_get_children_patch2_1196108_4783138.patch | 629 bytes | James_Stallings |
| #3 | taxonomy_get_children_patch1_1196108_4637958.patch | 629 bytes | James_Stallings |
Comments
Comment #1
jhodgdonThe version is intentional. We fix issues in the in-development version (which in this case is actually 8.x), not in specific versions of Drupal.
Comment #2
James_Stallings commentedLearning a bit about the taxonomy module this month :)
Comment #3
James_Stallings commentedComment #4
James_Stallings commentedComment #5
jhodgdonLooks OK... Punctuation/grammar nerdiness -- should be:
An array of term objects that are the children of the term $tid, or an empty array when no children exist.
(which -> that, and a comma before the 2nd clause)
Comment #6
James_Stallings commentedSure, I'll fix that tonight. How come your the only one to ever respond to these issues :P How large is the doc team?
Comment #7
jhodgdonThe docs team is fairly large actually, but most people in the docs team work on on-line documentation (the docs on drupal.org/documentation). The subset who work on API documentation on a regular basis is fairly small right now (you and a few other people), but highly appreciated!
As far as responding goes... Currently, I seem to be the only person who regularly reviews documentation patches -- you and the other team members mostly make patches. That seems to be working pretty well, though -- I have enough time to keep up with the reviews, and I definitely want to make sure the standards are being followed consistently... and as the Docs team leader responsible for the API docs, I am also interested in mentoring new contributors, getting them used to the standards, etc.
The other reason I end up being the person who responds is that I'm the person who triages the new issues in the documentation component of the Drupal Core issue queue, so I end up subscribed to nearly all of the documentation issues and get email when a new patch is submitted.
All of that said, if you would like to review docs patches, you can search for issues in the documentation component marked "needs review". There are some there that do need reviews (especially anything that I patched, since I can't review my own patches).
Comment #8
James_Stallings commentedComment #9
jhodgdonLooks good for 8.x/7.x, thanks!
Comment #10
webchickCommitted to 8.x and 7.x. Thanks! :)