Proposal: allow to map atoms to other values to handle null -> nil #154
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
Overbryd
force-pushed
the
master
branch
4 times, most recently
from
074c64d
to
52a95f7
Compare
…shortcuts to Poison.encode(value, iodata: true)
devinus
force-pushed
the
master
branch
2 times, most recently
from
ee06841
to
ee8336f
Compare
devinus
force-pushed
the
master
branch
20 times, most recently
from
60defaa
to
db4e965
Compare
devinus
force-pushed
the
master
branch
2 times, most recently
from
29a475d
to
e0a080a
Compare
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.
This is the best I could come up with, to handle JSON encoding for projects building upon a different world view (e.g. erlang dependencies classifying nil as
nullatoms).Related to that is this question posted on Stackoverflow: https://stackoverflow.com/questions/47895651/how-to-extend-an-existing-protocol-in-elixir/47901896
Outline
As a user of a JSON encoding library, I want to be able to specify atoms to be mapped differently at will to incorporate custom encodings depending on the applications/dependencies needs.
This solves a problem I was having encoding JSON with input coming from an erlang library using
:nullto encode what should benilin our world.Funny side note: "Null References The Billion Dollar Mistake"