Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync Client Config: resync mode #353

Closed
sync-by-unito bot opened this issue Mar 28, 2022 · 3 comments · Fixed by #925
Closed

Sync Client Config: resync mode #353

sync-by-unito bot opened this issue Mar 28, 2022 · 3 comments · Fixed by #925
Assignees

Comments

@sync-by-unito
Copy link

sync-by-unito bot commented Mar 28, 2022

No description provided.

@sync-by-unito
Copy link
Author

sync-by-unito bot commented May 16, 2022

➤ Desislava Stefanova commented:

Implemented in branch [resync_mode |https://github.com/realm/realm-dart/tree/resync_mode.] But it is not merged, because only Manual mode is supported for now.

@sync-by-unito
Copy link
Author

sync-by-unito bot commented Jul 25, 2022

➤ Desislava Stefanova commented:

Discard local changes mode is already available in core v12.3.0

@sync-by-unito
Copy link
Author

sync-by-unito bot commented Sep 8, 2022

➤ Brian Munkholm commented:

Enable "recoverOrDiscard" by default. Even without exposing other options.

desistefanova added a commit that referenced this issue Nov 4, 2022
Implements Client Resets support.
Added argument clientResetHandler when creating FlexibleSyncConfiguration. There are 4 possible handles that defines the mode of processing data in case of client reset:

RecoverOrDiscardUnsyncedChangesHandler
RecoverUnsyncedChangesHandler
DiscardUnsyncedChangesHandler
ManualRecoveryHandler
The default mode is RecoverOrDiscard.
Tests are added.

Fixes #353
Fixes #810
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant