Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
There are some places in the new entity query which is not documented perfectly, see http://drupal.org/node/1854708#comment-7069386 for example.
Comment | File | Size | Author |
---|---|---|---|
#7 | drupal-1918254-7.patch | 1.72 KB | dawehner |
#7 | interdiff.txt | 836 bytes | dawehner |
#5 | drupal-1918254-5.patch | 1.71 KB | dawehner |
#5 | interdiff.txt | 787 bytes | dawehner |
#3 | drupal-1918254-3.patch | 1.67 KB | dawehner |
Comments
Comment #1
dawehner.
Comment #2
jhodgdonThanks! A few things to fix:
- Needs newline between @param and @return sections.
- SQL is an acronym and needs to be all-caps in documentation. Actually though, I think rather than calling it a "sql field" (I had to think quite a while before I figured out what that meant), maybe this documentation should refer to constructing a database table field alias or something like that? I just thought that this phrase:
"a sql field for a given field"
was confusing, given that the word "field" has two meanings only a couple of words apart.
Comment #3
dawehnerThanks for the feedback. Yeah I was uncomfortable with that as well.
What do you think about this, is this easier to understand?
Comment #4
jhodgdonMuch better, thanks! I still don't really understand the return value documentation though:
An expression of the field and language, so for example "base_table.id".
Maybe something more like this would be clearer?
An expression that will select the given field for the given language in a SELECT query, such as 'base_table.id'.
Comment #5
dawehnerOh much much better!!
Comment #6
jhodgdonGlad we agree on the wording. One more thing: indent two spaces instead of one on @return docs.
Comment #7
dawehnerOh damn :) I'm feeling a bit like a novice starting the first contribution.
Comment #8
jhodgdonLooks good -- I'll get it committed soon (may need to wait for some Avoid Commit Conflicts issues first, but sometime soon). Thanks!
Comment #9
jhodgdonThis didn't conflict after all, so I committed it. Thanks again!