[wp-trac] [WordPress Trac] #44975: REST API support switching draft to unscheduled

[WordPress Trac]

#44975: REST API support switching draft to unscheduled
-----------------------------+------------------------------
 Reporter:  mnelson4         |       Owner:  (none)
     Type:  feature request  |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  REST API         |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  close            |     Focuses:
-----------------------------+------------------------------

Comment (by mnelson4):

 > No, the API and its clients should use a separate field for this
 purpose.

 Thanks for the feedback @jnylen0 and I mostly agreed, but you can see on
 #39953 that there's been quite a bit of resistance to adding a new field
 (not from me! See https://core.trac.wordpress.org/ticket/39953#comment:16.
 But I'm pretty un-opinionated and just want to help find a solution most
 people are happy with).

 >  I suggest closing this ticket as a duplicate of #39953.

 I opened this as a branch off of that ticket (see
 https://core.trac.wordpress.org/ticket/39953#comment:39) so that the
 currently-requested part of the feature (the ability to leave posts as
 "date-floating") can proceed un-impeded by this related-but-IMO-separate
 discussion. I'm pretty sure @kadamwhite ok'd this approach:
 https://wordpress.slack.com/archives/C02RQC26G/p1537482913000100.

 Having said that, if there's a complete reversal on #39953, and we do end
 up using a `date_floating` field, and we support this functionality using
 that field, then ya, we should close this ticket.

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