From 255c2d17a41d58957c627b3a459cb46377436eb6 Mon Sep 17 00:00:00 2001 From: stroblme Date: Thu, 20 Aug 2026 18:10:52 +0200 Subject: [PATCH] ROADMAP: node settings as arguments, and the flow boundary in the editor Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01NUb8YpL2s3gmN9WTACTt4q --- ROADMAP.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/ROADMAP.md b/ROADMAP.md index f2ba98b..16fccf4 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -199,6 +199,16 @@ React + Vite, primarily desktop but usable on mobile. See `docs/architecture/str that actually published rather than every producer of that message. A dashboard control, another flow or an API caller is drawn as a label on the canvas instead of being invisible — which also gives cross-flow wiring the link in/out it lacked +- [x] A node's settings are arguments of its function, next to its ports — one + `process(...)` signature covering both, no `params` dict, and a setting + sharing a port's name reported rather than shadowing it +- [x] A flow's boundary is on the canvas and in its panel: each declared input + is a label feeding what reads it (unless a control or another flow already + accounts for it), a batch flow's outputs hang off the end as its result, + and the panel edits mode, inputs and result — with the value a live flow + currently holds, and a way to put a new one in +- [x] Pressing Run on a batch flow asks for its parameters, prefilled from what + each input starts from, rather than quietly submitting the defaults - [x] Validation shown on the node it belongs to, and summarised in the dock - [x] Publish control and draft markers in the flow bar, discard in the flow panel, and a conflict dialog when another client got there first