Sending a document to the trash can fail for various reasons, one of
them being the absence of a trash (e.g. on Windows network shares).
In this case the document would remain in the user's local
synchronization directory while it's been deleted on their Cozy.
To prevent this state, we'll catch trash errors and try to permanently
delete the document.
In a second time, we might want to mark the trashed document on the
remote Cozy to alert the user that document might not be recoverable
from a local trash (if all connected Desktops's OSes don't have a
working trash for example).
Please make sure the following boxes are checked:
[x] PR is not too big
[x] it improves UX & DX in some way
[x] it includes unit tests matching the implementation changes
[x] it includes scenarios matching a new behaviour or has been manually tested
Sending a document to the trash can fail for various reasons, one of them being the absence of a trash (e.g. on Windows network shares).
In this case the document would remain in the user's local synchronization directory while it's been deleted on their Cozy. To prevent this state, we'll catch trash errors and try to permanently delete the document.
In a second time, we might want to mark the trashed document on the remote Cozy to alert the user that document might not be recoverable from a local trash (if all connected Desktops's OSes don't have a working trash for example).
Please make sure the following boxes are checked: