[wp-trac] [WordPress Trac] #43316: REST API: Support autosaves
WordPress Trac
noreply at wordpress.org
Fri Mar 30 16:30:58 UTC 2018
#43316: REST API: Support autosaves
-------------------------------------------------+-------------------------
Reporter: kraftbj | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: 5.0
Component: REST API | Version:
Severity: normal | Resolution:
Keywords: has-patch needs-testing needs-unit- | Focuses: rest-api
tests |
-------------------------------------------------+-------------------------
Comment (by azaozz):
Replying to [comment:56 schlessera]:
> What matters are the endpoints. I think that a `POST /posts/` is a
different concept than a `POST /autosaves/`.
> ...
> When we now split up `/posts/` to mean "trigger saving a post" AND
"trigger saving an autosave"...
Sorry I'm going to repeat myself but '''autosaving is''' "trigger saving a
post". It is the same concept of "saving a post", uses the same data
shape, form, and size, and performs the same action as a result of the
same intend by the client.
The logical problem in having `POST /autosaves/` endpoint is that it is
"superficial". Autosaves don't exist outside posts and revisions.
Anyway, think we delved into very "philosophical" discussion here :)
I'm assuming that:
- You are +1 on the patch that introduces an `autosaves` end point.
- Daniel is a +1 on the patch that adds autosave support to the `posts`
endpoint.
Anybody else?
--
Ticket URL: <https://core.trac.wordpress.org/ticket/43316#comment:57>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list