docs: clarify JSON parsing error conditions in Flask views #5826
+3
−2
Conversation
This file contains hidden or 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
Member
|
This doesn't address the linked issue, which talks about a specific error code, whereas this only rewords the existing sentence. The linked issue even has the suggested wording. It only required copying a sentence from one place to another, no writing required, no reason to reach for AI. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Update Documentation: JSON Parsing Behavior
Update the documentation to specify that JSON parsing fails for any reason, including a missing or incorrect
Content-Typeheader, not just invalid JSON or an unset header. This improves accuracy and clarity for developers.issue #5825