You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we modify a note, its ResourceId changes as well. This is expected since we use content-addressing. In order to provide proper UX, we need to track versions of the same note and present them to user as a single note. We also need UI elements to present older versions to user ("timeback machine"). User should be able to view or remove unwanted versions. Forking older versions into another note is separate feature.
Version storage must be stored in .ark/versions file and should look approximately like this:
Each entry of the file is a pair of ResourceIds, left id is parent and right id is child.
This feature needs a button to invoke list of versions, or "timeback machine", for any note. Each version must have a button to see its content (read-only mode), to remove it and to fork it (separate issue).
When we remove a version, we must keep the history unbroken.
Suppose, we have entries like this in storage:
3155416 -> 7705444
7705444 -> 8921986
If we want to remove 7705444 version, then we must replace these 2 entries with new entry:
3155416 -> 8921986
The text was updated successfully, but these errors were encountered:
When we modify a note, its
ResourceId
changes as well. This is expected since we use content-addressing. In order to provide proper UX, we need to track versions of the same note and present them to user as a single note. We also need UI elements to present older versions to user ("timeback machine"). User should be able to view or remove unwanted versions. Forking older versions into another note is separate feature.Version storage must be stored in
.ark/versions
file and should look approximately like this:Each entry of the file is a pair of
ResourceId
s, left id is parent and right id is child.This feature needs a button to invoke list of versions, or "timeback machine", for any note. Each version must have a button to see its content (read-only mode), to remove it and to fork it (separate issue).
When we remove a version, we must keep the history unbroken.
Suppose, we have entries like this in storage:
If we want to remove
7705444
version, then we must replace these 2 entries with new entry:The text was updated successfully, but these errors were encountered: