Improve deepobject unmarshalling to support nullable.Nullable and encode.TextUnmarshaler #45
Conversation
This file contains 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 #44.
This adjusts deep object unmarshalling to support types that implement
encoding.TextUnmarshaler(which fixes the issue with with unmarshalling uuid.UUID, and is an interface that is commonly implemented by other types). I'm aware that theBinderinterface exists however most types from common libraries don't/won't implement it.It also adjust deep object marshalling to support nil types, marshalling them as
field=nullrather thanfield=.Finally, it adds custom unmarshalling for the
nullable.Nullabletype. I'm not 100% happy with how I've done this, with thenullableLikeinterface, however becausenullable.Nullableis generic it's tricky to use casting/reflection to determine the type.