Property mapper function #118
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
Codecov Report
@@ Coverage Diff @@
## master #118 +/- ##
=======================================
Coverage 98.11% 98.11%
=======================================
Files 2 2
Lines 106 106
Branches 40 41 +1
=======================================
Hits 104 104
Misses 2 2
Continue to review full report at Codecov.
|
|
Great, thanks! |
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.
As discussed in #77 .
Had to change the logic in properties handling a bit, and introduced a new interface Properties. In addition, the Swagger2Definition interface is now exported from the top-level, as it is used in the mapper.
New tests added for the new functionality, all existing tests still passes. Readme is also updated.
Comments and suggestions welcome.