[wp-trac] [WordPress Trac] #40748: Use REST API for Community Events
WordPress Trac
noreply at wordpress.org
Wed May 24 00:50:59 UTC 2017
#40748: Use REST API for Community Events
-------------------------------------------------+-------------------------
Reporter: iandunn | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Future
Component: REST API | Release
Severity: normal | Version: trunk
Keywords: has-patch dev-feedback needs-unit- | Resolution:
tests | Focuses: javascript
-------------------------------------------------+-------------------------
Comment (by jnylen0):
Replying to [comment:12 azaozz]:
> This is a "mostly" private end point. We don't plan on maintaining 100%
backwards compatibility and don't recommend for plugins to reuse. It may
(and probably will) change in 4.8, 4.9, etc.
>
> One of the original ideas was to also add a front-end (standard) widget
people can put on their sites. This can happen in the future and would
mean things are likely to change a bit.
>
> I'm not sure what would be the best way to pass this message to plugin
authors that may think to reuse the endpoint. Would that be in the schema
somewhere? (Having this would also be quite helpful as a precedent for
plugins.)
AFAIK this doesn't exist yet. We could add a flag, or we could say that
anything under the `dashboard/v*` namespace is not subject to the same
backwards compatibility expectations as `wp/v2`, and document this
carefully.
I question why we want to go ahead and say that we won't maintain
backwards compatibility for this endpoint, though. Shouldn't we try
anyway? Isn't that the whole point of the `/v1` versioning mechanism (new
endpoints would be `/v2` or `/v1.1`, and the old ones would stay in
place)?
--
Ticket URL: <https://core.trac.wordpress.org/ticket/40748#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list