Fix 4 openapi20 and30 #55
Open
Conversation
This file contains 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
…s like x-* (case of Redoc extensions)
in case of content-type <> JSON, simple declare:
@apiSuccess {String} 200
the swagger schema will use this string type directly without creating intermediate object
Fix bad // treatment
…ansformation with enum definition ( compatible with openapi2.0 and 3.x).
- correct Number range detection in the special case of {Number{-1-n}} definition id apidoc
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.
Correct syntax of array of strings constrained on enum values (compatible with OAS2.0 and OAS3.x)