Unwrap Jackson2 Array and Object Nodes in JsonNodeValueResolver (#964, #969) - #965
Unwrap Jackson2 Array and Object Nodes in JsonNodeValueResolver (#964, #969)#965carusology wants to merge 2 commits into
Conversation
carusology
commented
Apr 10, 2022
@jknack: What do you think of this update to the |
carusology
commented
Apr 21, 2022
Added a fix for #969 as well since it's basically the same problem but on JSON objects instead of JSON arrays. After a JSON object is converted to a I fixed it in a distinct commit following the same "lazy" pattern of resolution and added a test. |
carusology
commented
May 11, 2022
( •_•)σ @jknack Any objections? If not, is there a release guide? I don't mind going through the machinations. |
mynameisjeoff
commented
Aug 12, 2022
@jknack would we be able to get an update on this pull request or is there someone else who would be able to review these changes before they can be merged in? |
carusology
commented
Oct 24, 2022
mimranfaruqi
commented
Aug 27, 2024
Hi, any updates as to when this PR could be merged? I have somewhat similar problem that Thank you |
Background
This is a fix for self-reported issue #964. Now the
JsonNodeValueResolverresolves a Jackson2ArrayNodeas aList<Object>with its items being recursively resolved.I wrote it in the same style as the
JsonNodeValueResolver.toMap()method, meaning:JsonNode.Testing
I wrote a few unit tests to verify the behavior works as expected. All of the existing unit tests pass without issue.