5 Commits

Include renames

Author	SHA1	Message	Date
stroblme	4c15f4abe1	Test hygiene: empty the flow store between modules, unbind demand on shutdown, poll the hook state in test_flow_ids, count only the watcher under test in the revoked-link test, delete runs.spec's runs	2026-11-05 08:03:56 +01:00
stroblme	fa15522cb0	Frontend addresses flows and dashboards by id: routes /flows/$flowId, /dashboards/$id and /view/$id, query keys, saves, lists, device pickers, search, brain and endpoint links and generated results dashboards go by id, while live values, issues, pauses and message names keep the key; tabs take the title from the document; creating uses POST and opens the issued id; the flow and dashboard panels show key and id with a copy button and a served HTTP or WebSocket node shows its hook URL under the flow id; specs create by POST and ids.spec.ts exercises issued ids	2026-11-02 19:57:43 +01:00
stroblme	6ad249bfb3	Let the search reach past the twentieth of a kind, and unbreak two specs ... The global search capped each category before cmdk had matched anything, so nothing past the twentieth node or widget could be found at all — this instance has 28 nodes and 97 widgets. The cap now trims the candidates the query could reach rather than the raw index. The admin teardown asked /users/ for limit=1000, which the route stopped accepting when its bounds went in; a 422 body has no `data` to iterate, so the hook threw and took the tests it was attributed to with it. It asks for the 500 the route allows. And `submit` folds every declared initial into a run's params, so an input the run never passed can no longer read as the flow's own. That assertion is gone; what the panel does show — the value the run actually started from, passed or not — is what the test checks.	2026-09-06 14:46:59 +02:00
stroblme	954496de0d	New run: start a run from the app, on the working copy ... The site promises simulated inputs and mocked sensor values, and nothing in the app was that. A run already is: the values are the caller's, the state is the run's own namespace, and nothing it computes reaches the live flow. What was missing was a screen to do it from, and the draft flag being honoured. `/runs/new` is a flow, a field per declared input, a seed and Run; `/runs` stays the log. A comma-separated list in a number field expands into the grid `fluksio sweep --param` builds and goes to the sweep route, so launching one no longer needs a terminal. Only numbers split: a comma in a string is content, and one in JSON is syntax. `RunCreate.draft` was validated at submit and dropped before the run executed, so "try the working copy" ran the published one. `Run.draft` is a column now, the driver reads the same copy the submit checked, and a retry carries it. `FlowSummary.mode` came with it so the rail can say which flows are batch before one is picked. Also here: a Retry button on a finished run, which the route has always had and the UI never did, and parameter cells truncated to their column with the full value on hover.	2026-09-02 15:10:24 +02:00
stroblme	8fa66039ce	Act on a run, and read Home top-down ... Runs: a run can now be deleted (DELETE /runs/{id}, cancelling a live one first), exported as csv from the screen's own filters, and its flow label opens the flow. Its "Parameters" panel became "Inputs" and lists every input the flow declares, marking the ones that took the flow's own value rather than the run's — the comparison table resolves the same defaults instead of printing "unset". Home reads brain, dashboards, health, flows: the mosaic is one full-width scrolling strip, and the flows list and the flow-activity rollups merged into a single left-joined table so a flow's state and its numbers sit on one row. Charts take a drag to narrow the x window and a double click or tap to come back out. UplotChart holds the scale and passes resetScales:false while a window is held, which is what the old comment said made this impossible.	2026-08-29 08:37:11 +02:00