[buddypress-trac] [BuddyPress Trac] #7156: Build REST-API endpoints for all Components.

buddypress-trac noreply at wordpress.org
Tue Mar 19 11:53:30 UTC 2019

#7156: Build REST-API endpoints for all Components.
 Reporter:  DJPaul                  |       Owner:  (none)
     Type:  feature request         |      Status:  new
 Priority:  strategic               |   Milestone:  5.0.0
Component:  REST API                |     Version:
 Severity:  normal                  |  Resolution:
 Keywords:  needs-docs needs-codex  |
Changes (by espellcaste):

 * keywords:   => needs-docs needs-codex


 Just passing by to inform that all endpoints for the `before-bp-merge` and
 `v1` milestones are done, reviewed and ready:

 A lot of work was put into it in the past two years! So I'm very excited
 about that!

 There are, however, some components that don't have endpoints yet. Those
 will be added in the next BuddyPress release.


 Those are the components with endpoint support:
 * Activity
 * Group Membership
 * Group Membership Request(s)
 * Group Avatar
 * Group Invites
 * XProfile Fields
 * XProfile Groups
 * XProfile Data
 * Members
 * Members Profile Photo (aka Avatar)
 * Notifications
 * Components


 > technical decisions about how we merge into core (leave as external
 project vs moving to SVN, where it lives in the filesystem, etc)

 I'd recommend keeping at GH, at least until the next version of the API is
 ready, just like the BP CLI and BP Default.

 If everyone agrees, I can have a patch ready with an example of the
 implementation. :)


 Another important task pending is documentation. @boonebgorges and I have
 been testing some options. But a page at the Codex will also be necessary
 with basic information and probably a link to the actual doc of the API.

Ticket URL: <https://buddypress.trac.wordpress.org/ticket/7156#comment:5>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac

More information about the buddypress-trac mailing list