Fluksio/app - app

6 Commits

Author	SHA1	Message	Date
stroblmeandClaude Fable 5	3fa9141eb9	Scope the node-type fixture check to the built-ins Playwright Tests / test-playwright (1, 2) (push) Canceled after 0s Details Playwright Tests / test-playwright (2, 2) (push) Canceled after 0s Details pre-commit / pre-commit (push) Canceled after 0s Details Test Backend / test-backend (push) Canceled after 0s Details Compose Smoke Test / test-compose (push) Canceled after 0s Details Playwright Tests / merge-reports (push) Canceled after 0s Details Installing the connectors made this fail, which is the test working: it insists every offered type is exercised. But a connector is a separate package with its own tests, so it is not this suite's to cover. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011LF61rxW1FG5YCD2J9YqjY	2026-08-16 11:16:41 +02:00
stroblmeandClaude Fable 5	85abf58337	Count flows rather than nodes in the health report is keyed by node id, so a four-node flow reported four flows. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011LF61rxW1FG5YCD2J9YqjY	2026-08-16 11:15:49 +02:00
stroblmeandClaude Fable 5	42075a6dae	Give a connector node an icon that is not a code icon A device read over a proprietary protocol was showing the fallback used for a function node. A connector's type cannot be in the built-in icon map — that is the point of it being a connector — so they share a plug. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011LF61rxW1FG5YCD2J9YqjY	2026-08-16 11:14:35 +02:00
stroblmeandClaude Fable 5	4de3cd7c66	Record the connectors and what is still read-only Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011LF61rxW1FG5YCD2J9YqjY	2026-08-16 10:00:10 +02:00
stroblmeandClaude Fable 5	be6d4fc13c	Build dashboards you can actually look at and press Widgets bind to a message name and read it live off the socket the editor already had — lifted out of the flow editor so a dashboard route gets the same values, which also gives the home page live data for free. The input widgets close the loop the other way: a slider publishes into the graph and whatever consumes that message runs. Verified end to end in the running app — moving a slider set a flow input, and the stat bound to what the flow computed from it followed. View mode is plain CSS grid. A wall panel that only displays should not download the code that lets someone drag things around, and it now does not. Editing is a widget picker, a per-widget width control and a settings card fed by the message catalog. No new dependencies: the slider is a range input, the gauge is an arc, and the markdown is a five-line subset. Charts are the one widget still missing — they need a charting library and the chart tokens the design guidelines reserved — so they are stored and validated but not offered. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011LF61rxW1FG5YCD2J9YqjY	2026-08-16 09:33:02 +02:00
stroblmeandClaude Fable 5	895bd89b2b	Dashboards as documents, and messages as something to bind to A dashboard is its own document rather than widgets placed in a flow. Node-RED's dashboard tab is 260 nodes, about forty of them pure layout, which is exactly what the small-graph principle exists to avoid — and since the graph is already wired by message name, a widget can bind to a name without belonging to any flow. Stored beside the flows in the same repository, sharing their write lock and commit, under a directory the flow listing ignores. No draft/publish split: nothing executes a dashboard, so edit mode is its own staging area. Two things it needs from the engine. A message catalog spanning every flow, because a wall panel shows the heating next to the solar and the flow-scoped API is the wrong shape for that. And a way to put a value in without owning a node — a slider is a real value that happened to come from a person — which runs whatever consumes it and applies the same type check a node's output gets. Only a message some flow declares can be published to; flows own the namespace. Charts also need more past than the 120 points a sparkline wanted, so a chart widget declares its depth and the engine keeps that message's series that deep. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011LF61rxW1FG5YCD2J9YqjY	2026-08-16 09:20:49 +02:00