Add content field support for path, query, header, and cookie parameters#26
Merged
Flowneee merged 2 commits intoMay 21, 2026
Merged
Conversation
Parameters now accept an optional `content` field (media type string, e.g. "application/json"). When set, the macro emits `ParameterValue::Content` with a single-entry media type map instead of `ParameterValue::Schema`, in compliance with the OpenAPI 3.0 spec. Backward-compatible: existing `schema`-only usage is unchanged.
Contributor
Author
|
@Flowneee review plz |
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.
Parameters now accept an optional
contentfield (media type string, e.g. "application/json"). When set, the macro emitsParameterValue::Contentwith a single-entry media type map instead ofParameterValue::Schema, in compliance with the OpenAPI 3.0 spec.Backward-compatible: existing
schema-only usage is unchanged.