-
Notifications
You must be signed in to change notification settings - Fork 465
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
feat(persist): Deep merge records in batchUpdate #3386
Conversation
@@ -59,7 +59,7 @@ describe('Supervisor', () => { | |||
void supervisor2.start(); | |||
|
|||
await vi.waitUntil(() => tickSpy1.mock.calls.length > 0, { | |||
timeout: 5000 | |||
timeout: 10000 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Had this one fail on me in dev again, so I went ahead and bumped it up a good bit more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good and simple 👍🏻
I'm not sure it's really clear for an end user, there is no way to optin or optout, this might break some expectation (or be unnoticed)
Currently
batchUpdate
only shallow merges. This switches it to deep merge, as request by some customers.I want to get @bastienbeurier's take on docs strategy here, but code is ready for review.
See https://linear.app/nango/issue/NAN-1982/partial-records-update
How I tested it
batchUpdate
in a subsequent run to merge them.