Explain how to send nested objects when style serialization fails - #141
Merged
mromaszewicz merged 1 commit intoJul 12, 2026
Merged
Explain how to send nested objects when style serialization fails#141mromaszewicz merged 1 commit into
mromaszewicz merged 1 commit into
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
Refs: #52 Styling a parameter whose object schema contains a nested object failed with a bare "unsupported type Header", which gives no hint that the spec itself defines no wire format for this. OpenAPI style-based serialization covers only primitives, arrays, and flat objects; complex values are meant to use the parameter's content form (e.g. `content: application/json`). When a struct or map reaches primitiveToString without satisfying any of the serialization escape hatches, the error now says exactly that and points at declaring the parameter with `content: application/json` (or mapping the schema to a Go type implementing fmt.Stringer). Behavior is otherwise unchanged: nested objects still fail to serialize, by design. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
Refs: #52
Styling a parameter whose object schema contains a nested object failed with a bare "unsupported type Header", which gives no hint that the spec itself defines no wire format for this. OpenAPI style-based serialization covers only primitives, arrays, and flat objects; complex values are meant to use the parameter's content form (e.g. content: application/json).
When a struct or map reaches primitiveToString without satisfying any of the serialization escape hatches, the error now says exactly that and points at declaring the parameter with content: application/json (or mapping the schema to a Go type implementing fmt.Stringer). Behavior is otherwise unchanged: nested objects still fail to serialize, by design.