Recommend synchronous DELETE requests return 204 #41
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Open
|
I think by virtue of it being a guide, it has a huge caveat emptor label over everything anyway. My personal feeling about this is that it should be prescriptive (and it all pretty much is so far), because leaving stuff open to interpretation means varying qualities of implementation. |
|
I would also prefer a single prescriptive option, wherever possible. I think the exceptional case would be synchronous vs asynchronous. That said, one of my colleagues is pulling on a few extra threads in #15 that I'd like to continue discussing a bit more before we decide which possibility we think is best. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I feel like we've reached enough of a consensus in #15 to attempt to PR a change, so this fixes #15.
Wording has been changed to suggest all responses should provide the latest copy of the data, further suggesting that (synchronous)
DELETEs should return a204 No Content.