fix: name a step inside a subflow sub:inner in flow tests (#12549)

Matches the sub:inner id the flow graph shows for a step of an expanded
subflow, and avoids reading like a field of the step's result.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Ruben Fiszel
2026-11-19 19:18:16 +01:00
committed by GitHub
co-authored by Claude Opus 5.5
parent 5583c680d4
commit 50daf70337
11 changed files with 17 additions and 15 deletions
+1 -1
View File
@@ -1856,7 +1856,7 @@ def test_flow(
- a top-level function of the calling script's own file: the step runs that function instead
of its own code, with the step's inputs as keyword arguments.
A step inside a subflow is named by the path of step ids to it, ``"sub.inner"`` for step
A step inside a subflow is named by the path of step ids to it, ``"sub:inner"`` for step
``inner`` of the subflow that step ``sub`` calls. It applies to every call of that subflow
made by the tested flow and by the subflows it overrides; a subflow left as is still calls
the deployed one. Those subflows, and each one on the way to an override, run as you rather