Fix minor issues after introducing incremental JSON_PATCH merge#284
Conversation
Co-authored-by: Tim Golen <tgolen@gmail.com>
|
@marcaaron @tgolen all review comments adressed! 👍 |
tgolen
left a comment
There was a problem hiding this comment.
Thanks for those changes. You'll get the hang of the comments in time, so keep working on them!
|
+1 to @tgolen's comments about comments :)
Also, I think this is a part that could be better explained in the comments as well. |
Ah i understand, didn't know, that that's why we added this manually for web. Gonna further explain this in the comments then! |
When building the batch of changes, we don't want to omit the null keys, because then this would happen: Changes like For creating the |
Co-authored-by: Tim Golen <tgolen@gmail.com>
marcaaron
left a comment
There was a problem hiding this comment.
One small thing that needs to be addressed. Looks good - thanks for the changes!
|
One last thing 🥲 |
fixed! |
mountiny
left a comment
There was a problem hiding this comment.
Thanks @tgolen and @marcaaron for pushing this forwards.
To unblock the other onyx caching PR, I am going to approve and merge this, given Tim already gave approval and the last changes requested by Marc has been addressed and they were just comments.

@marcaaron
Details
Fixing some issues i encountered while testing the
JSON_PATCHmerge changes in theExpensify/Apprepo in this PRWhen batching the changes from
mergeQueue, top-levelnullvalues may not be omitted. Only when merging the final value, we can remove thesenullvalues.Also added back a log line, that was removed in the other PR
Related Issues
Automated Tests
Linked PRs