[buddypress-trac] [BuddyPress Trac] #7156: Build REST-API endpoints for all Components.
buddypress-trac
noreply at wordpress.org
Sun Jun 23 16:17:34 UTC 2019
#7156: Build REST-API endpoints for all Components.
----------------------------------------------+--------------------------
Reporter: DJPaul | Owner: espellcaste
Type: feature request | Status: accepted
Priority: strategic | Milestone: 5.0.0
Component: REST API | Version:
Severity: normal | Resolution:
Keywords: needs-docs needs-codex has-patch |
----------------------------------------------+--------------------------
Comment (by imath):
Thanks a lot for your feedbacks @espellcaste
About version change, I think we just need to increase the version number
of the BP REST plugin once BuddyPress 5.0.0 is released for instance:
- 0.1.0 => 5.0.0
- 0.1.1 => 5.1.0
- 0.2.0 => 6.0.0
About unit tests, I'd say final merge because you need them to carry on
developing the remaining endpoints from GitHub in this scenario. (it helps
doing a first "review" of PRs)
About the `@todo`: I think it can be removed because the function is
already using the filterable path. I've read the history of the file and,
the `@todo` appeared in [https://github.com/imath/BP-
REST/commit/40b12887f3441c8c37772d07c43738c8d7c15438#diff-
f81f3dff36bf04b7a070d642c858e883 40b1288] but wasn't removed in
[https://github.com/imath/BP-
REST/commit/a305cf779502057b5ed4505b8e951f3d47f4753e#diff-
f81f3dff36bf04b7a070d642c858e883 a305cf7]
About svn export, SVN trunk == GIT master 😉. It's the way to do it.
--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/7156#comment:10>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac
More information about the buddypress-trac
mailing list