[wp-trac] [WordPress Trac] #43316: REST API: Support autosaves
WordPress Trac
noreply at wordpress.org
Thu Apr 12 14:25:05 UTC 2018
#43316: REST API: Support autosaves
-------------------------------------------------+-------------------------
Reporter: kraftbj | Owner: rmccue
Type: enhancement | Status: assigned
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 adamsilverstein):
Some good points have been made here and its time to take stock of all the
feedback and move forward! The lack of any autosave capability is a
blocker for merging Gutenberg because without it autosaves are essentially
broken.
My intuition and initial idea was a separate Autosave controller. Still,
I liked the idea of adding autosave capability to the revisions controller
(as @rmccue suggested in 43316.13.diff) because of their technical
similarity, or even adding to the posts controller with a flag as
originally proposed in 43316.patch by @azaozz...
However from the client's perspective these actually seem like pretty
different concepts. As @schlessera keeps pointing out, its the difference
in the ''concepts of autosave vs. revision vs post'' that suggests a
separate autosave endpoint is appropriate. The fact that technically
autosaves are very similar to revisions and even posts is an
implementation detail that doesn't concern clients.
To those on this thread advocating alternate approaches, can you agree to
moving ahead with a separate Autosaves controller (latest in
43316.12.diff​) and if not, what blocking concerns remain?
--
Ticket URL: <https://core.trac.wordpress.org/ticket/43316#comment:75>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list