Make bulk row moves atomic
This commit is contained in:
@@ -80,6 +80,7 @@ Intent is separated by drag source type:
|
||||
- cross-section reorder is rejected
|
||||
- bulk device row move:
|
||||
- supported via multi-selection + drag
|
||||
- row assignments, optional target creation and reserve-state updates are committed in one SQLite transaction
|
||||
- multi-circuit move:
|
||||
- supported for same-section selected circuit blocks
|
||||
|
||||
@@ -125,4 +126,3 @@ Current limitations:
|
||||
|
||||
- session-local only
|
||||
- no persisted history across browser reload
|
||||
- some multi-step backend flows are not fully transaction-hardened end-to-end
|
||||
|
||||
@@ -5,7 +5,6 @@
|
||||
- No global cross-project device library workflow is implemented yet.
|
||||
- Final electrical sizing logic is not implemented yet.
|
||||
- No full norm-compliant voltage-drop and protection-dimensioning calculation flow yet.
|
||||
- Bulk device-row move flow is command-based but not fully transaction-hardened end-to-end across all affected circuits.
|
||||
- Sorting is view-only until users explicitly apply sorted order.
|
||||
- Cross-section circuit drag-reorder is intentionally blocked.
|
||||
- Legacy consumer and circuit-first paths coexist; migration is transitional and still requires operational discipline.
|
||||
|
||||
Reference in New Issue
Block a user