Decision: a memo is up to three files #7
No reviewers
Labels
No labels
area/agent
area/capture
area/editor
area/geo
area/security
area/sync
area/transcription
area/ui
area/vault
area/voice-memos
blocked
milestone/M1
milestone/M2
milestone/M3
milestone/M4
needs-decision
needs-hardware
p0
p1
p2
type/bug
type/enhancement
type/feature
type/idea
type/infrastructure
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Stash/stash-docs!7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "m2-05-a-memo-is-three-files"
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?
The filenames, the shared parts folder and its numbering, and which path may delete which file.
Recorded here because these are the cross-client contract: the vault's inbox processing, Android
and anything else that ever reads a Stash folder are reading these names, and the reasoning
otherwise lives only in an iOS branch.
The part most likely to be got wrong by a later client is who may delete what. The obvious
implementation — one list of "files this app wrote" — has transcript finalisation unlinking route
parts on the ordinary stop, which is data loss that only shows up after the fact.
The GPX element layout is not in here. That is a separate decision, recorded with the work that
writes the first track (Stash/stash-ios#34).
Companion to Stash/stash-ios#32.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.