Feature/model in response refactored #2583
Merged
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
frantuma
force-pushed
the
feature/modelInResponse_refactored
branch
from
8453ff5 to
9a536ca
Compare
…ema instead of Property as schema in Response Object.
gracekarina
force-pushed
the
feature/modelInResponse_refactored
branch
from
44817df to
8b97df3
Compare
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.
This PR includes:
Utils class in core module: converter property to model and model to property
Changes in Response model in models module: added an attribute schemaAsModel type Model,
deprecated getSchema, setSchema methods. added method for new attribute.
Use converter in response model.
Related- issues: swagger-api/swagger-parser#567
swagger-api/swagger-parser#488