[wp-trac] [WordPress Trac] #43316: REST API: Support autosaves

[WordPress Trac]

#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 adamsilverstein):

 @danielbachhuber thanks...

 > If the shape of the data is the exact same, then we could co-opt the
 status attribute to trigger an auto-save (i.e. status=auto-save).

 The shape of the data is identical - its a post thats being saved, both
 for posts and for autosaves. The problem with status is an autosave can
 have a published or draft status, we need to store the status. In
 https://core.trac.wordpress.org/ticket/43316#comment:10 @azaozz proposed
 using post type as the 'flag' that triggers an autosave. see
 [attachment:43316.1.diff]


 > Generally, in thinking about this more, I'd be leaning closer to one
 revisions endpoint that covers past and future revisions.

 So, add the ability to explicitly create revisions?


 > Right now, it's difficult to understand the decisions and consensus
 through all of the Trac comments and patches.

 I agree - and there was additional discussion in
 [https://wordpress.slack.com/archives/C02RQC26G/p1520345228000158 slack]
 around this ticket as well.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/43316#comment:49>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform