This repository was archived by the owner on Mar 13, 2025. It is now read-only.
Persist null updates on embedded fields #660
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Our team has noticed that null values do not persist when unsetting nested embedded fields, unless the field is an
EmbeddedCollection. After debugging the code, we noticed that the pathways forEmbeddedandEmbeddedCollectionwere slightly different:EmbeddedCollectionPathwaydef embeddedUpdate = encodeUpdate(o, createEntityAccess(o), EncoderContext.builder().build(), true)This call to
encodeUpdatepasses throughembedded = true.EmbeddedPathwaydef embeddedUpdate = encodeUpdate(v)This call to
encodeUpdatedefaults toembedded = false.Root cause of failure to unset null fields on updates
The
unsetsarray never receives theprop.namekey of the embedded fields going through theEmbeddedpathway, because of the following code:Solution
This PR passes through
embedded = truein both theEmbeddedandEmbeddedCollectionpathways.