Let users specify if/how None values are encoded #126
Merged
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 #125.
Changes proposed in this pull request:
encode_none
parameter toQuery
which lets users specify if at all, and if yes how a value ofNone
should be sent to the service.This changes behavior slightly: if a parameter is
None
(per its default value or because the user set it), previously it was encoded as...?name=None
. To retain this behavior, a user would have to specifyQuery(..., encode_none="None")
.Attention: @prkumar