[buddypress-trac] [BuddyPress Trac] #6366: In `BP_User_Query`, allow xprofile fields to be toggled when searching

[buddypress-trac]

#6366: In `BP_User_Query`, allow xprofile fields to be toggled when searching
--------------------------+-----------------------------
 Reporter:  boonebgorges  |       Owner:
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:  Future Release
Component:  API           |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |
--------------------------+-----------------------------
Changes (by boonebgorges):

 * milestone:  2.3 => Future Release


Comment:

 I spent a little more time thinking about this, and, as is often the case,
 it's not as easy as it sounds.

 What would this look like at the API level? In the case of `wp_users`
 fields, people would probably want to be able to pass an array of fields
 to match: `array( 'user_login', 'user_nicename' )`. What does this look
 like for xprofile? Do we accept field names, or field IDs, or both? Since
 xprofile fields can be created at will by the admin, perhaps a more likely
 use for xprofile is to pass a *blacklist* rather than a whitelist of
 fields: match all fields *except* for x, y, z. Is this a separate param?
 Is there any purpose to having an 'exclude' param for `wp_users`, when the
 group of available fields is so small?

 Gotta think more about this :(

--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/6366#comment:2>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac