Per-folder and per-file disconnect #55
Labels
No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda#55
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #37. Shares machinery with ignore rules.
What Relay does
Right-click a folder to disconnect it as a persistent setting; a satellite icon
disconnects a single file; a manual "sync" pulls on demand. Their issue #18
covers the on-demand mode.
What we do today
A folder is mapped or unmapped, and that is the whole granularity. Unmapping is
in the settings tab; there is nothing per-file and no context menu.
What changes
A persisted exclusion set honoured by
vault-watcher.ts,content-sync.tsandfile-sync.ts, surfaced as a context-menu toggle and an explorer indicator.Same plumbing as ignore rules, same hazard: disconnecting must never read as
deleting to anyone else.
Risk
risk:none.Verification
As for ignore rules — the other vault's copy survives, and the test fails when
inverted.
Moved to the Vikunja board as NEC-32: https://projectron.nerchure.com/tasks/32