Uh oh!
There was an error while loading. Please reload this page.
Use "stepId" instead of Symbol.for("STEP_FUNCTION_NAME_SYMBOL") for annotating step functions - #341
Conversation
🦋 Changeset detectedLatest commit: 2288833 The changes in this PR will be included in the next version bump. This PR includes changesets to release 11 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for GitHub.
|
| configurable: false, | ||
| } | ||
| ); | ||
| Object.defineProperty(stepFunction, 'stepId', { |
There was a problem hiding this comment.
Curious why this isn't also a symbol, e.g. Symbol.for('WORKFLOW_STEP_FUNCTION_STEP_ID') or similar. I guess it's unlikely people will patch this property onto their functions manually so totally fine
There was a problem hiding this comment.
It's for consistency with how we annotate workflow functions with workflowId. This PR is more of a cosmetic change.
6786aac to
e8fe109Compare8e9a498 to
75e95adComparee8fe109 to
5eb588aCompare75e95ad to
2c7bbdfCompare… annotating step functions
2c7bbdf to
2288833CompareUh oh!
There was an error while loading. Please reload this page.

Replace
Symbol.for("WORKFLOW_STEP_FUNCTION_NAME")with a standardstepIdproperty for step function annotation.What changed?
STEP_FUNCTION_NAME_SYMBOL(a Symbol) with a regularstepIdproperty on step functionsstepIdproperty instead of the SymbolSTEP_FUNCTION_NAME_SYMBOLconstant from symbols.tsWhy make this change?
This more closely resembles how Workflow functions are annotated with a
workflowIdproperty.