-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Conversion of MissingNode
throws JsonProcessingException
#4932
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
Comments
Sounds sub-optimal. I'll need to think about expected behavior: probably should be converted to "absent value" (which most often is |
Hi Cowtowncoder, thank you for considering I admit my expected behavior is only because of the documentation I cited. It does not necessarily have to be null. For comparison: |
Right, 100% agreed on now throwing exception. I think I'll go with |
MissingNode
throws JsonProcessingException
Uh oh!
There was an error while loading. Please reload this page.
According to the documentation about MissingNode the following holds:
While this holds true for most operation, this fails when converting a json tree containing a MissingNode to a Pojo.
Version Information
2.18.0
Reproduction
Expected behavior
Expected behavior:
converting a MissingNode should behave the same as converting the NullNode
Observed behavior:
converting a NullNode returns a null reference.
converting a MissingNode throws a JsonProcessingException.
The text was updated successfully, but these errors were encountered: