add default (de)serializer for Literal values #180
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.
I implemented these for a project I'm working on that uses
jsons
, then noticed #170 and figured I may as well see if you like the implementation enough to go with it.I included the
strictly_equal_literal
as a compromise between correctness and utility.From https://peps.python.org/pep-0586/#equivalence-of-two-literals
I took that to mean that for a value to really match a literal it should match in both type and value. The only problem with that is that I've found it to be very useful to allow
jsons
to "coerce" values that are equal in value into the literal value, the use case that prompted me to implement this actually relies on that behaviour.