Stop and start a flow without rebuilding anything

A stopped flow's nodes are built like any other flow's — being stopped
means having no subscriptions, schedules or webhooks, not being absent —
so a toggle only ever needed the lifecycle call and the gate that goes
with it. It was doing a whole-pipeline rebuild instead, which on a
populated installation is every node in every flow reconnecting.
This commit is contained in:
2026-08-23 18:35:28 +02:00
parent 56d836cd7a
commit 57804de645
3 changed files with 80 additions and 3 deletions
+4 -1
View File
@@ -13,7 +13,10 @@ Deferring because out of scope is fine, but don't mention deferring than.
### Dashboard UI rework (dedicated session)
Rework the dashboard UI to make it more flexible in terms of the look and feel.
I consider following design options a) overall appearance: material look or liquid glass (einUI https://github.com/einui/einui) b) color palette
I consider following design options a) overall appearance: material look or liquid glass (einUI https://github.com/einui/einui) b) color palette (https://plotly.com/python/discrete-color/).
Based on a) and b) it should be possible to derive almost endles combinations of looks.
The color palette should affect charts/gauges and other widgets
### To be sorted