Duplication Check
How Should It Be Like?
The "Awaiting confirmation" dialog opens with Select all already checked and presents every operation in one flat, scrollable tree. Downloads, uploads and deletions are distinguished only by icon colour, with the legend above the list.
When the operation count is large this makes destructive operations easy to miss. In my case the visible part of the list showed a folder of PDFs marked as conflict resolutions; several dozen local deletions were further down, already selected, and I never scrolled to them. I confirmed, and the deletions propagated to the device that held the only complete copy of the vault — 59 notes, which were not recoverable from the trash either (see #232).
Two changes would have prevented this without adding friction to the common case:
- A summary line above the tree, for example
12 downloads · 3 uploads · 59 local deletions · 0 remote deletions. Counts of destructive operations should be readable without scrolling.
- Deletions unchecked by default. Non-destructive operations can stay pre-selected as they are now; deletions would require an explicit opt-in, either individually or through a "select all deletions" control.
Optionally, a warning when deletions exceed some proportion of the vault. A sync proposing to delete most of the local files is nearly always a misconfiguration rather than an intent.
To be clear, the plugin behaved as configured, and confirmTasksInSync is what gave me the chance to stop it at all. This request is about making that safeguard readable exactly when it matters most — when the operation list is long.
How Would It Work?
The operation list already exists as structured task data before the dialog renders, so the counts can be derived by task type without extra bookkeeping, using the same classification that drives the icon colours.
For the default selection state, the initial checked set would exclude removal tasks rather than defaulting to everything, leaving the existing selection controls untouched.
I have not implemented this and am not proposing a detailed design — happy to test a change against the scenario above.
Duplication Check
How Should It Be Like?
The "Awaiting confirmation" dialog opens with Select all already checked and presents every operation in one flat, scrollable tree. Downloads, uploads and deletions are distinguished only by icon colour, with the legend above the list.
When the operation count is large this makes destructive operations easy to miss. In my case the visible part of the list showed a folder of PDFs marked as conflict resolutions; several dozen local deletions were further down, already selected, and I never scrolled to them. I confirmed, and the deletions propagated to the device that held the only complete copy of the vault — 59 notes, which were not recoverable from the trash either (see #232).
Two changes would have prevented this without adding friction to the common case:
12 downloads · 3 uploads · 59 local deletions · 0 remote deletions. Counts of destructive operations should be readable without scrolling.Optionally, a warning when deletions exceed some proportion of the vault. A sync proposing to delete most of the local files is nearly always a misconfiguration rather than an intent.
To be clear, the plugin behaved as configured, and
confirmTasksInSyncis what gave me the chance to stop it at all. This request is about making that safeguard readable exactly when it matters most — when the operation list is long.How Would It Work?
The operation list already exists as structured task data before the dialog renders, so the counts can be derived by task type without extra bookkeeping, using the same classification that drives the icon colours.
For the default selection state, the initial checked set would exclude removal tasks rather than defaulting to everything, leaving the existing selection controls untouched.
I have not implemented this and am not proposing a detailed design — happy to test a change against the scenario above.