Improve synchronization (don't lose tasks) #4843
ltguillaume
started this conversation in
Ideas
Replies: 3 comments
-
|
Thank you! I am all for improving this, once the dust with the current sync problems has been settled :) |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
thanks for this great app I find this issue super annoying tbh, why 2 diffrent tasks cause a merge conflict |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Link this to the relevant FR/issue about all this: #4857 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Situation
Keep remote), or those from step 3 (Keep local).Possible solution
Edit: For ready-made conflict-free sync implementations, see #4857.
Apart from the ideal situation of implementing a journaling approach, where every operation is recorded, allowing for granular syncing, implementing the following should be an improvement:
modifiedattribute against each local task's: newer remote tasks overwrite local; older remote tasks are synced to the remote; same timestamp is no action.modificationattribute: if themodificationattribute in the removed tasks list is newer, the task is also removed on the syncing device, otherwise the task is "restored".This would already be significantly more granular and would prevent a lot of cases where actual data loss or/by conflict dialogs would otherwise occur.
Beta Was this translation helpful? Give feedback.
All reactions