Uh oh!
There was an error while loading. Please reload this page.
fix(studio): flow wait-node inspector tolerates the loose config shape - #1974
Merged
Conversation
The wait inspector read only `waitEventConfig.{eventType,signalName,…}`, but the
engine also accepts the looser `config.{eventType,…}` shape that the canonical
showcase_budget_approval (and AI-authored flows) use — so a showcase-shaped wait
node showed blank fields in the designer.
Flow config fields gain `fallbackPath`: tolerant read (loose shape displays +
dependent fields reveal), canonical write that prunes the fallback
(migrate-on-edit), and the fallback config key suppressed from Advanced. The
`wait` fields fall back to `config.*`. Designer now matches engine tolerance.
Refs #1954 (ADR-0044).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>Uh oh!
There was an error while loading. Please reload this page.
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
✅ Console Performance Budget
📦 Bundle Size Report
Size Limits
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
A wait node authored with the loose
configshape —config: { eventType: 'signal', signalName: '…' }— rendered blank "Wait for" / "Signal name" fields in the flow designer. The wait inspector read only the spec-canonicalwaitEventConfig.{…}, while the engine accepts both (waitEventConfig.eventType ?? config.eventType). The canonicalshowcase_budget_approvalrevise-loop wait node uses exactly the loose shape — so the designer was stricter than the engine, hiding valid config (and AI-authored flows that learn from the showcase hit the same blank-field gap).Change
Flow config fields gain an optional
fallbackPath:getFieldValuefalls back to it when the canonical path is empty, so loose-shape wait nodes display and dependent fields (showWhen) reveal.setFieldwrites the canonicalpathand prunes thefallbackPath, so editing converts a loose node to the canonical shape (no stale duplicate; engine + designer agree).configkey is claimed inownedConfigKeys, so it never shows up in the Advanced-JSON block.The
waitfields (eventType/timerDuration/signalName/timeoutMs/onTimeout) fall back toconfig.*. The designer now matches the engine's tolerance.Verification
flow-node-configtests 9 passing (3 new: canonical read; loose-configfallback + dependent-field reveal; canonical-wins-when-both).setField(field, …)signature change — single call site).type-check0 errors;eslint0 errors (pre-existingset-state-in-effectwarnings untouched).Pairs with the ADR-0044 revise-loop authoring (#1954); the framework side normalizes the showcase + automation skill to the canonical shape separately.
🤖 Generated with Claude Code