-
Notifications
You must be signed in to change notification settings - Fork 128
Add support for closure scope vars in step functions #358
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,8 @@ | ||
| --- | ||
| "@workflow/web-shared": patch | ||
| "@workflow/swc-plugin": patch | ||
| "@workflow/world": patch | ||
| "@workflow/core": patch | ||
| --- | ||
|
|
||
| Add support for closure scope vars in step functions |
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
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
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
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
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,18 @@ | ||
| import { contextStorage } from './context-storage.js'; | ||
|
|
||
| /** | ||
| * Returns the closure variables for the current step function. | ||
| * This is an internal function used by the SWC transform to access | ||
| * variables from the parent workflow scope. | ||
| * | ||
| * @internal | ||
| */ | ||
| export function __private_getClosureVars(): Record<string, any> { | ||
| const ctx = contextStorage.getStore(); | ||
| if (!ctx) { | ||
| throw new Error( | ||
| 'Closure variables can only be accessed inside a step function' | ||
| ); | ||
| } | ||
| return ctx.closureVars || {}; | ||
| } |
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing backward compatibility handling for step input format. The code assumes
hydratedInputhas anargsproperty, but old steps created before this change will havestep.inputas a serialized array, causing a runtime error when trying to access.args.View Details
📝 Patch Details
Analysis
Missing backward compatibility handling for step input format in stepEntrypoint
What fails: stepEntrypoint() in runtime.ts lines 684 and 707 assume
hydratedInputhasargsandclosureVarsproperties. When old steps created before the closureVars feature was added are replayed, they havestep.inputas a serialized array (not wrapped in an object). Upon hydration, this returns the array directly, and accessing.argson an array returnsundefined. This causes line 686args.lengthto throw:TypeError: Cannot read properties of undefined (reading 'length')How to reproduce:
step.input = dehydrateStepArguments([arg1, arg2], globalThis)(just an array){ args, closureVars }hydrateStepArguments(step.input, ...)const args = hydratedInput.argswhich isundefinedon an arrayargs.lengthonundefined, throwing TypeErrorExpected behavior: Code should handle both:
{ args: [...], closureVars: {...} }[...]This pattern is already implemented in observability.ts line 63:
'args' in hydratedInput ? hydratedInput.args : hydratedInputFix applied: Added defensive checks that mirror the observability.ts pattern:
This ensures backward compatibility with steps stored in the old format while supporting the new closureVars feature.