[wp-trac] [WordPress Trac] #29642: Support complex (nested, multiple relation) queries in WP_Meta_Query
WordPress Trac
noreply at wordpress.org
Sat Oct 11 17:45:04 UTC 2014
#29642: Support complex (nested, multiple relation) queries in WP_Meta_Query
------------------------------------+------------------
Reporter: boonebgorges | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: 4.1
Component: Options, Meta APIs | Version:
Severity: normal | Resolution:
Keywords: has-patch dev-feedback | Focuses:
------------------------------------+------------------
Comment (by boonebgorges):
After some thought and some discussion with nacin in IRC, I've decided to
step back from the `WP_Recursive_Query` proposal for the time being.
`WP_Meta_Query` will remain standalone for now.
[attachment:29642.4.patch] updates 3.patch with:
* Improved organization (to better match the other classes)
* Improved inline documentation
Before pulling the trigger on this, I'd like to have some feedback from
DrewAPicture on the documentation aspect. It's a bit tricky to capture the
nested nature of the params given our hash standard. I chose to do a few
things:
1. Move the parameter documentation to the `__construct()` method
2. In the hash format, describe a "first order" clause, but then make
reference to the fact that you can also pass "fully-formed" meta queries
as parameters.
3. In the docblock for the class, I go into a little more detail and give
a brief example for illustration.
4. I fixed up (I think) the parameter default documentation, using the
format:
{{{
@type type $foo Description description description. Default: 'bar'.
(bar|baz|barry)
}}}
--
Ticket URL: <https://core.trac.wordpress.org/ticket/29642#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list