Please use the 👍 reaction to show that you want to have the same feature implemented.
Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
Subscribe to receive notifications on status change and new comments.
Feature description
The macOS VFS sync engine will currently handle conflicts in very naive ways. For example, incoming file-name clashes will lead to the new file being ignored. Similarly, with files that have changed both locally and on the server, the file provider sync engine will always choose to push the local changes
We should more gracefully detect these conflicts and allow the user to resolve the issue by creating actionable conflict files (and maybe a conflict dialog)
How to use GitHub
Feature description
The macOS VFS sync engine will currently handle conflicts in very naive ways. For example, incoming file-name clashes will lead to the new file being ignored. Similarly, with files that have changed both locally and on the server, the file provider sync engine will always choose to push the local changes
We should more gracefully detect these conflicts and allow the user to resolve the issue by creating actionable conflict files (and maybe a conflict dialog)