Handling of nulls with Number differs from encoding/json #184

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

Closed

oschwald opened this issue Oct 6, 2017 · 0 comments

oschwald commented Oct 6, 2017

This is similar to #181, but for null. encoding/json unmarshals a null value to json.Number("") while jsoniter returns an error:

readNumberAsString: invalid number, parsing 53 ..."", "t5": ... at {"test":"blah", "t2":472, "t3":"473", "t4":"", "t5": null}

The text was updated successfully, but these errors were encountered:

taowen closed this as completed in

16f7860

zhenzou pushed a commit to zhenzou/jsoniter that referenced this issue


          fix json-iterator#184, support null as number

121607d

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment