Improve conflict handling in macOS Virtual Files module Sync Engine #6835
Labels
enhancement
enhancement of a already implemented feature/code
feature: 馃捊 virtual filesystem
os: 馃崕 macOS
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)
The text was updated successfully, but these errors were encountered: