Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Elixir/Erlang nil/null problem #82

Closed
grepz opened this issue Mar 11, 2019 · 2 comments
Closed

Elixir/Erlang nil/null problem #82

grepz opened this issue Mar 11, 2019 · 2 comments

Comments

@grepz
Copy link
Contributor

grepz commented Mar 11, 2019

Having some problems with elixir/erlang null/nil coding/decoding.
Jiffy has wonderful option use_nil, which does following:

 jiffy:encode(#{a => nil}, [use_nil]).
<<"{\"a\":null}">>

Why not use same approach in msgpack? Having similar option that handles nil/null as one entity. Changes in code are minimal.
@grepz grepz mentioned this issue Mar 12, 2019
Merged
@grepz
Copy link
Contributor Author

grepz commented Mar 12, 2019

#83

kuenishi pushed a commit that referenced this issue Jun 9, 2023
@grepz
Issue #82 (#83)
14df9be 
* Erlang/Elixir nil/null issue addressed similar to jiffy use_nil approach.

* README updated.

* use_nil additionality implemented for unpack method.
@kuenishi
Copy link
Member

kuenishi commented Jun 9, 2023

Thanks @grepz , this issue has been fixed as of 0.8.1.

@kuenishi kuenishi closed this as completed Jun 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kuenishi @grepz