Add device row move history
This commit is contained in:
@@ -25,14 +25,20 @@ concurrency checks.
|
||||
|
||||
The public dispatcher currently supports `circuit.update`, `circuit.insert`,
|
||||
`circuit.delete`, `circuit-device-row.update`,
|
||||
`circuit-device-row.insert` and `circuit-device-row.delete`, all with schema
|
||||
version `1`. Other command types are rejected. Insert commands contain the
|
||||
complete entity or circuit block with stable ids; delete commands include the
|
||||
expected parent identity. Circuit snapshots contain zero, one or multiple
|
||||
complete device rows. This makes deletion undoable without generating
|
||||
`circuit-device-row.insert`, `circuit-device-row.delete` and
|
||||
`circuit-device-row.move`, all with schema version `1`. Other command types are
|
||||
rejected. Insert commands contain the complete entity or circuit block with
|
||||
stable ids; delete commands include the expected parent identity. Circuit
|
||||
snapshots contain zero, one or multiple complete device rows. Move commands
|
||||
contain each row's expected and target circuit plus its exact expected and
|
||||
target sort order. This makes deletion and moves undoable without generating
|
||||
replacement identities or renumbering circuits. The editor does not consume
|
||||
these endpoints yet.
|
||||
|
||||
`circuit-device-row.move` currently targets existing circuits in the same
|
||||
circuit list. Creating a new target circuit while moving rows is not yet part
|
||||
of the persistent command API.
|
||||
|
||||
Example:
|
||||
|
||||
```json
|
||||
|
||||
Reference in New Issue
Block a user