Bugfix/issue 673 missing properties body parameter convertion parser #688
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
ralphdoe
requested review from
gracekarina and
webron
and removed request for
gracekarina
…nto bugfix/issue-673-missing-properties-body-parameter-convertion-parser
gracekarina
deleted the
bugfix/issue-673-missing-properties-body-parameter-convertion-parser
branch
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.
Tests in Converter to Check if the new Properties added in the: swagger-api/swagger-core#2768 are being converted.
There's a dependency in the Swagger Parser Master PR: #687
The SwaggerDeserialize changed to consider this new properties.
Related issue: #673