This repository has been archived by the owner on Mar 3, 2020. It is now read-only.
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 change allows
Point
to deserialize coordinates provided as strings rather than numbers (floats or ints).I'm serving an API using webargs/flask and I'm using a NestedQueryFlaskParser as suggested in the docs.
I receive a query like this one:
The custom parser generates a dictionary but does not deserialize the coordinate values into numbers.
I guess marshmallow-mongoengine's
Point
is the right place to do that. Or am I wrong?@touilleMan, @kevin0571 any advice?