Persist circuit cell edits
This commit is contained in:
@@ -390,6 +390,9 @@ Implemented foundation:
|
||||
- a central application dispatcher reconstructs persisted commands and exposes
|
||||
optimistic command, undo and redo endpoints for Circuit and CircuitDeviceRow
|
||||
field updates
|
||||
- the circuit tree exposes `currentRevision`; existing Circuit and
|
||||
CircuitDeviceRow cell edits use those optimistic commands and project-wide
|
||||
undo/redo instead of direct field-update PATCH routes
|
||||
- typed CircuitDeviceRow insert/delete commands preserve complete row snapshots
|
||||
and stable ids; row mutation, circuit reserve state, revision and history
|
||||
stack transition commit or roll back together
|
||||
@@ -424,10 +427,11 @@ Implemented foundation:
|
||||
- integration coverage verifies sequential revisions, stale-command rejection
|
||||
and rollback after a forced late persistence failure
|
||||
|
||||
ProjectDevice CRUD, synchronization and disconnect on the project page are
|
||||
connected to this history boundary. The circuit-list editor and the remaining
|
||||
domain writes are not fully connected; its visible undo/redo therefore remains
|
||||
session-local until the remaining tasks are implemented.
|
||||
ProjectDevice CRUD, synchronization and disconnect on the project page and
|
||||
existing Circuit/CircuitDeviceRow cell edits in the circuit-list editor are
|
||||
connected to this history boundary. Remaining structural editor writes are not
|
||||
fully connected; the editor's visible undo/redo stack therefore remains
|
||||
session-local and is not reconstructed after reload.
|
||||
|
||||
Acceptance criteria:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user