Fixed issue where a field that was removed from a Record would still exist after a merge. #67
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.
This could happen when a value changed to
null
. This fixes a bug in the following scenario:x
has valuey
. The result is cached.x
has valuenull
.Expected Result: field
x
has valuenull
.Actual Result: field
x
still has valuey
.The fix was to ensure that keys/fields that do not exist in a new record are removed from the old record during a merge.