Repository navigation
docs: clarify JSON media type defaults and strict migration - #605
Merged
Merged
Conversation
Owner
Author
|
Merge authorized by the maintainer’s explicit instruction. Reviewed documentation against body policy tests; no default change. Exact head 60dfada: all five required contexts completed=success; no unresolved review threads. Local make check-all build: 767 passed, 27 deselected, 4 warnings in 19.84s; 97.16% coverage. |
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
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.
Summary
Make strict JSON Content-Type configuration obvious without changing compatibility defaults.
Changes
Document application/json and structured +json acceptance, text/plain and missing-header behavior, non-empty 415 and empty-body 422 outcomes. Expand relaxed-default coverage across all four header classes. Describe client-first per-route migration and require a separate breaking-release decision before changing defaults; no warning or vulnerability claim is introduced.
Validation
Python 3.11 make format check-all build passed: 767 passed, 27 deselected, 4 warnings in 19.84s; coverage 97.16%. Existing strict Content-Type cases pass. No production behavior change. GitHub CI pending.
Related Issues
Closes #597
Merge authorized by the maintainer’s explicit instruction.