facett-file — crate card
Reverse-engineered (from source — verify, don't trust the name)
- One-line pitch: A pure-egui file-attachment facet: a drop zone plus an attachment list.
- Does: Renders a drop zone and a list of
FileRefs (name, size, mime) with remove buttons; aread_onlymode disables editing. Reports intents only —take_added()/take_removed()for the host to apply — and does no file I/O itself. In the ärende profile an attachment is a handling; the legal metadata (direction, diarienummer, sekretess) lives on the case, not here. Facet contract (title/ui/state_json). - Key deps: egui, serde/serde_json (no chrono). Optional
facettfeature. - Shape: lib, ~216 LOC single lib.rs (FileRef, Files).
- Observed role in the workspace: Standalone upload/list widget, no in-repo consumer yet. Built in ordning; destined for facett.
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: