Support strict
setting in all decoders
#434
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.
This adds a new
strict
boolean config kwarg to alldecode
functions (as well as allDecoder
classes). The default isTrue
, matching the existing strict type coercion rules. Setting toFalse
enables a wider set of coercion rules, which may be useful in some scenarios. Currently settingstrict=False
enables coercing:"null"
(case insensitive) toNone
"false"
or"0"
(case insensitive) toFalse
"true"
or"1"
(case insensitive) toTrue
Additional coercion rules may be added to
strict=False
("lax mode") in the future.Note that coercion still only happens if the requested type (e.g.
int
) doesn't match the provided type (e.g.str
). When not usingmsgspec.json.decode
without a type specified no coercion will happen.Fixes #424.