Repository navigation
[Website] Document the 16.7 response format selection changes - #10459
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
The migration guidance is complete and no unresolved issues were identified.
Review effort: Lite
Findings: None
What changed in this PR
Documents the 16.7 response format negotiation changes and migration impact.
Changes:
- Explains
Acceptquality values andq=0handling. - Documents single and streaming response behavior.
- Clarifies envelope tie-breaking and bodyless
406responses.
| File | Description |
|---|---|
website/content/docs/hotchocolate/migrating/migrate-from-16-6-to-16-7.md |
Adds response format migration guidance and behavior examples. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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
Acceptheader's quality values, aq=0media type is never chosen, and a single result is written asmultipart/mixedortext/event-streamonly when the header names that media type or itstype/*range.@deferand@streamresults. The entry also states that a tie between the two envelopes goes tomultipart/mixed, and when a406has no body.main, under theLegacyand default transport versions.