This repository was archived by the owner on Sep 24, 2018. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 24, 2018. It is now read-only.
Disambiguate between trashed and permanently deleted Posts and Comments #1260
Description
Activity
#1271 should help out with this for now, but we want to also wrap the data in an object with a
trashed/deletedkey. This intentionally won't match the data itself, since we're not returning the resource as-it-currently-is, but rather as-it-was-before-the-call-executed.Let's bump to b3 though, as we might want to be semi-consistent with #1196 (e.g. use
datain both)?Punted to Beta 4
After a little bit of discussion, we're going to return the original resource instead of wrapping it in a
dataobject.🚢 🚢
In
develop, a client making aDELETErequest to Posts or Comments has no way of distinguishing between whether the request trashed the resource or permanently deleted it. We should provide this detail.From #1224
Also, 2x
DELETE wp/v2/comments/<id>will permanently delete a comment, but 2xDELETE wp/v2/posts/<id>will return somerest_already_deletederror (2d5cf2c, #959). We should make sure these are consistent.