[buddypress-trac] [BuddyPress Trac] #9145: Move the BP REST API into BuddyPress core
buddypress-trac
noreply at wordpress.org
Mon Jul 22 16:48:51 UTC 2024
#9145: Move the BP REST API into BuddyPress core
--------------------------------------+--------------------------
Reporter: espellcaste | Owner: espellcaste
Type: task | Status: assigned
Priority: normal | Milestone: 15.0.0
Component: REST API | Version:
Severity: normal | Resolution:
Keywords: has-patch has-unit-tests |
--------------------------------------+--------------------------
Comment (by imath):
Thanks for your explanations @espellcaste I think I misunderstood your
intent. I thought just like the WP REST API, going v2 would mean
**deprecating v1** (see #comment:1 the `Version 1 could be deprecated`
part).
Reading your explanations, I understand you want to maintain each possible
version of the BP REST API. It's great, but it requires a lot more work.
You took Woocommerce as an example, this project has 1,396 contributors
listed on their GitHub repository, we have 17 contributors listed on ours:
this makes me think we should consider more reachable expectations, for
example: actively maintain the latest version of the BP REST API (and
deprecate all previous ones). I think we should try to keep things as
simple as possible for us and for the people who will come after us.
I personally think a "more than 5 years" inconsistency is becoming a
strong motive to go v2 😅.
My suggestion is to do one bigger change, instead of 2 successive changes.
But I'm open to different opinions, as your first intent for this ticket
was to simply move v1 here, if the majority of team members also think we
should only do that: I can wait for a v2, but the more we wait, the more
it will be difficult to deal with making the change (waiting 10 years for
rewrites already showed this to us).
--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/9145#comment:10>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac
More information about the buddypress-trac
mailing list