Repository navigation
Support openapiV3 oneOf for fields/responses - #1671
Merged
Merged
Conversation
ubogdan
approved these changes
Nov 7, 2023
Contributor
|
@kkkiio Thanks for your contribution |
ubogdan
added a commit
that referenced
this pull request
Nov 7, 2023
|
Hi @kkkiio instead of swaggo version: v1.16.3 |
Contributor
Author
|
Unfortunately, the PR was reverted due to a compile error. I may create a new PR to address this. Please note that the |
Merged
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.
Describe the PR
Adds support for the oneOf feature in OpenAPI v3, allowing you to describe a field/response that can have multiple types.
Relation issue
Close #1363
Close #1617
*Additional context
Example: