-
Notifications
You must be signed in to change notification settings - Fork 51
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.
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
Deserialization depends on lexicographical ordering of types #296
Comments
Ok, I digged into it a bit. This seems to come down to the comment here: Lines 70 to 89 in 02e2ecf
And JSON3.jl not failing when there are extra fields. So JSON3.read("{\"name\":\"test\",\"n\":1}", Type2) does not fail.Might we add a keyword argument ignore_extra_fields::Bool=false to JSON3.read to opt into throwing an error when an extra field is encountered?
|
Is there more work to do or did the PR resolve this issue? |
No, this is resolved as far as I'm concerned. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is unexpected and may be a bug.
The parsing as
Type2
in the second example drops one field of the json data.The text was updated successfully, but these errors were encountered: