This repository was archived by the owner on Apr 23, 2025. It is now read-only.
feat(OAS 3-requestBody): Support for OAS 3 requestBody as customValue#45
Open
osvaldo2627 wants to merge 1 commit intogoogle:masterfrom
Open
feat(OAS 3-requestBody): Support for OAS 3 requestBody as customValue#45osvaldo2627 wants to merge 1 commit intogoogle:masterfrom
osvaldo2627 wants to merge 1 commit intogoogle:masterfrom
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Allows the specification of a requestBody as a customValue for [POST, INT, PUT] methods.
For example:
I know that parsing parameters relays on the sway implementation. But "requestBody" from OAS 3 is still not supported and for OAS-3.X is not a parameter anymore.
What do you think about having this here?