jappel/leistungsbilanz-ts
1
0
Fork 1
Code Issues 6 Pull requests Projects Releases Packages Wiki Activity Actions
leistungsbilanz-ts/docs/circuit-list-editor-known-limitations.md
Grovy311 94688d7a8c Add print view, board info card and document logo upload 
- Seitenansicht (/projects/:projectId/print): tabular cover page, board
  overview with supply structure and power sums, one plan per board with a
  repeating title block; PDF via the browser print dialog with named @page
  rules (A4 portrait cover, A4/A3 landscape plans, page x of y).
- Distribution-board info card (board number, location, fed-from, remark)
  in the board edit dialog, persisted through the additively extended
  distribution-board.update command (migration 0008, snapshot schema 6,
  legacy subtree commands normalized).
- Global document logo upload (PNG/JPEG/SVG, max 2 MB) outside project
  revisions and snapshots.
- fed-from stays free text; the overview hierarchy and cumulated sums are
  preliminary until the feed link is modeled.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25 19:31:36 +02:00

2.4 KiB
Raw Blame History

Circuit List Editor Known Limitations

  • All currently supported Circuit and CircuitDeviceRow editor writes use persistent project commands and project-wide toolbar undo/redo, including moves, atomic multi-section reorders and explicit renumbering. Undo/redo eligibility is restored from server history after a page reload.
  • The project page exposes the paginated revision timeline; the circuit editor itself currently exposes only the next eligible Undo/Redo actions.
  • Named and automatic logical project snapshots can be listed and restored through the project page with persistent Undo/Redo. Automatic snapshots are created every 25 revisions and only their newest 12 entries are retained.
  • The Revit/CSV foundation and confirmed initial import are implemented. Existing-row assignment, move and detach plus creation of an external-only row in an existing or newly created circuit have atomic persistent commands. Their API planning and editor UI, follow-up import, conflict review and return export are pending.
  • Persistence currently targets local SQLite; PostgreSQL is an architectural option, not an implemented runtime.
  • The global device library supports basic CRUD and copy operations, but has no versioning, permissions or controlled synchronization model.
  • Final electrical sizing logic is not implemented yet.
  • No full norm-compliant voltage-drop and protection-dimensioning calculation flow yet.
  • Sorting is view-only until users explicitly apply sorted order.
  • Complete-circuit drag supports one circuit at a time between groups of the same category. Cross-category moves and multi-circuit moves across group boundaries are intentionally rejected; multi-circuit reorder inside one group remains supported.
  • Protection and cable values are planner-owned manual selections. The later sizing/warning engine does not yet validate them against load, length or voltage-drop rules.
  • Distribution-board fedFrom is free text. The print overview derives its supply structure and "Σ inkl. unterlagert" only from exact text matches with board numbers/names and adds values without an upstream simultaneity factor (see docs/print-view.md).
  • The print view cover page shows placeholders for address, Leistungsphase and office staff, and uses a provisional kbp corporate design. On screen, long board plans are not split into pages; pagination happens in the browser print dialog.