facett-kanban — crate card
Reverse-engineered (from source — verify, don't trust the name)
- One-line pitch: A pure-egui Kanban board facet: status columns, drag-to-transition, swimlanes, WIP limits.
- Does: Renders cases as draggable
Cards inColumns (one per workflow status), optionally grouped into swimlanes (assignee/priority/kind) with per-column WIP limits. Dragging a card to another column records aMove; the host drainstake_moves()to fire (and validate) the real workflow transition.Boardfollows the facett Facet contract (title/ui/state_json); the widget itself does no state mutation of the domain. - Key deps: egui, serde/serde_json. Optional
facettfeature (off by default) toimpl facett_core::Facet; compiles egui-only otherwise to stay robust against facett-repo churn. - Shape: lib, ~386 LOC single lib.rs (Column, Card, Priority, Move, Board).
- Observed role in the workspace: Consumed by
ordning-gui::kanban_view(the only widget with an in-repo consumer). Built in ordning temporarily; destined for the facett repo.
Fill in (one line each — only the human knows these)
- Primary consumer(s):
- Why it exists (vs the obvious alternative):
- Hard constraint (airgap / no-C-deps / no-FFI / pure-Rust / etc.):
- Release cadence & independence (rides a parent? own repo someday?):
- Status (production / prototype / experimental / stubbed):
- Must-NOT-change invariant:
- Biggest known gap or TODO:
- Anything a newcomer would get wrong about it: