Persist section renumbering
This commit is contained in:
@@ -129,8 +129,8 @@ undo/redo calls the project-wide server history. New entities receive stable
|
||||
UUIDs before insertion, and deletion undo restores those same ids. Device-row
|
||||
moves and circuit reorders also use persistent project commands. Applying a
|
||||
sorted view across multiple sections is atomic and occupies one history step.
|
||||
Renumbering still uses its direct API write and session-local inverse callback
|
||||
during the cutover.
|
||||
Explicit renumbering uses a collision-safe persistent project command and one
|
||||
project-history step.
|
||||
|
||||
Covered operations include:
|
||||
|
||||
@@ -144,5 +144,3 @@ Covered operations include:
|
||||
Current limitations:
|
||||
|
||||
- the visible editor stack is still session-local and is empty after reload
|
||||
- renumber editor actions are not connected to the persistent command boundary
|
||||
yet
|
||||
|
||||
Reference in New Issue
Block a user