17. History, versions and comments
Esta página está em inglês; a tradução está a caminho.
| ID | Requirement | P | Type | Ver. | M |
|---|---|---|---|---|---|
| COL-1 | A history panel shall list changes. From the WAL: who, when, what, grouped by session; preview the document at any point; restore a point as a new change. | Must | functional | test | 0.3 |
| COL-2 | Named versions shall be saved. “Save to version history” with a title and description; listed in history and in ud versions; consolidation keeps them. |
Must | functional | test | 0.3 |
| COL-3 | Comments shall be pinned to the canvas. Threads anchored to a node or a point, with mentions of git authors, reactions, resolve/reopen; stored in the file; listed in a panel; ud comments. |
Should | functional | test | 0.6 |
| COL-4 | Two branches shall merge. git union merge of the WAL (*.design merge=union in .gitattributes, offered by the extension); concurrent edits of different properties both survive; the same property resolves last-in-file wins and is reported. |
Must | functional | test | 0.1 |
| COL-5 | Branch compare shall be visual. “Compare with branch/revision” shows changed frames side by side with an overlay (CMD-35). | Should | functional | demonstration | 0.6 |
| COL-6 | Live co-editing could be offered through VS Code Live Share. The host’s editor is the single writer; guests send commands over a Live Share service and see cursors and selections. | Could | functional | demonstration | backlog |