From 40e9db2d56a3ba42f87440a2345007d5ef36457a Mon Sep 17 00:00:00 2001 From: stroblme Date: Thu, 20 Aug 2026 21:04:35 +0200 Subject: [PATCH] up Signed-off-by: stroblme --- NOTEPAD.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/NOTEPAD.md b/NOTEPAD.md index 87c4990..b4d2911 100644 --- a/NOTEPAD.md +++ b/NOTEPAD.md @@ -166,7 +166,7 @@ as an em dash. - CHORE/UI: only `layout.lg` is ever written, and `md`/`sm` stay unwritten by decision — a phone stacks the widgets (`.widget-stacked`) rather than carrying an arrangement of its own, since arranging is not a phone feature. The keys stay in the schema for a panel that one day wants a second size. - PERF/UI: `ChartWidget` re-joins the whole table on every live value. Fine at IoT rates; at `HISTORY_CAP` × 5 series it should append into a ring buffer. - CHORE/UI: opening edit mode on a dashboard whose widgets predate placement writes the migrated positions immediately, bumping the version once. -- CHORE/API: creating a dashboard publishes it straight away (an empty document goes to the panels), while a new flow starts as a draft. Keeps `read`/`list` free of a never-published case, at the cost of the asymmetry. +- CHORE/API: creating a dashboard publishes it straight away (an empty document goes to the panels), while a new flow starts as a draft. Keeps `read`/`list` free of a never-published case, at the cost of the asymmetry. NOTE: we should change this such that dashboards stay drafts until they get published - PERF/UI: "Publish all" reads each document's detail for the version its publish must match, so a click is 2N requests. A bulk endpoint, or a `version` on the summaries, would make it one. ### Flow editor follow-ups