nextcloud / nextcloud/nextcloudfileproviderkit
Handle sync conflicts without data loss
Open
@i2h3 is already working on this.
Since Jul 17, 2025.
- Dominant language
- Swift
- Stars
- 8
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
At present, the macOS virtual files client implements a very simple form of conflict handling: the latest remote changes are down-synced, replacing local changes. Conversely, the latest local changes will always replace the file's state on the server. Your task is to implement sync conflict handling that avoids data loss. A successful submission of this task will demonstrate handling of sync conflicts that provide users with safe and clear approaches with which to handle sync conflicts, avoiding data loss.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.