Fluksio/app
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Flow inputs carry an origin hint, run or panel

Browse Source 
The Inputs editor and the canvas label show it, and the run forms leave
panel inputs out.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WgBfkm4rCmtd1T4vHWjEPx
This commit is contained in:
stroblme
2026-10-15 10:08:46 +02:00
co-authored by Claude Opus 5.5
parent ccc7081b08
commit f5be932df3
10 changed files with 111 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/concepts/values.md
+4 -2
View File
@@ -47,8 +47,10 @@ The initial value seeds an unset live message. Later publications take over;
changing the starting value does not overwrite a value already in state.
Use **Publish this value now** in the input row to send it immediately.
The canvas draws flow inputs as labelled endpoints. Without a producer or
declared input, a consuming node reports `unconnected_input`.
The canvas draws flow inputs as labelled endpoints, marked `run` or `panel`
by what writes them. A panel input is one a dashboard or panel control writes,
and the run form does not ask for it. Without a producer or declared input, a
consuming node reports `unconnected_input`.
A batch flow's inputs are run parameters. Its **Result** section selects the
messages returned when the run finishes. See [Runs](runs.md).