WIP: Adds support for string to collection coercion based on collectionFormat#94
Open
WIP: Adds support for string to collection coercion based on collectionFormat#94
Conversation
e1df7ec to
7f03367
Compare
Member
|
LGTM |
Member
|
This should be merged? |
Member
Author
|
Only if the todo items are implemented. |
|
@Deraen Any plans to complete this? I'd be eager to use it. I guess the best alternative now is to spec the param to string and do parsing in the app? |
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 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.
Fixes #69
TODO:
coercerfunction which returns matchers instead of coercer so they only run single layer of coercions instead of doing recursive coercioncollection-formatinstead ofcollectionFormat. Maybe json-schema should do key transformations so that snake-case can be used here?