[wp-trac] [WordPress Trac] #40748: Use REST API for Community Events
WordPress Trac
noreply at wordpress.org
Tue May 30 02:49:12 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 rmccue):
Replying to [comment:13 jnylen0]:
> 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.
This is basically the plan. `dashboard/` would be the prefix for endpoints
just for the "dashboard app", which wouldn't meet the same design
standards or back compat guarantees. That said, I don't think we'd
necessarily have to just break backwards compat, we can continue iterating
just like any API. (We could also continue to do the standard deprecation
in release `n`, but then actually commit to removing it in release `n+1`.)
`dashboard/` is basically the same as us creating internal PHP classes or
functions called `_wp_...`.
(See [https://github.com/WP-API/proposals/pull/1 the proposal] which would
also add docs to the core contributor handbook; we can add further docs as
well.)
----
I'll update the patch to re-add the schema back in, since it seems like we
still want that.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/40748#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list