Changes between Initial Version and Version 1 of Ticket #44975, comment 14
- Timestamp:
- 07/29/2019 05:39:33 PM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #44975, comment 14
initial v1 1 1 > I am in favor of this ticket, and believe the appropriate response to accept to restore floating date status would be null, 2 2 3 Accepting `null` absolutely makes sense: inserting null for these crates the `floating` date (it is the default database value for these fields). Not sure about accepting `false` or `''` - `null` seems more explicit. 3 Accepting `null` makes sense: inserting null for these crates the `floating` date (it is the default database value for these fields). 4 5 One potential issue however is that `null` is the same as not sending any value at all for the field, right? This might lead to unexpected behavior if clients weren't always sending the `post_date_gmt` field. Perhaps sending `false` is more explicit, I'm curious what precedent exists in other endpoints and APIs.