feat(workflow): Expose updateId to update handlers #1450
Merged
Conversation
This file contains 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
mjameswh
reviewed
Jun 25, 2024
mjameswh
reviewed
Jun 25, 2024
mjameswh
reviewed
Jun 25, 2024
mjameswh
approved these changes
Jun 28, 2024
# for free
to join this conversation on GitHub.
Already have an account?
# 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 was changed
A method
currentUpdateInfo()has been added to workflow to obtain the name and id of a currently executing update handler from within. The solution uses AsyncLocalStorage to propagate this information across asynchronous invocations. CallingcurrentUpdateInfo()within a workflow, but outside the async scope of an update handler invocation, returnsundefined.Why?
Facilitate deduplication of updates, particularly across CAN boundaries.
Checklist
[Feature Request] Expose
updateIdto Update handlers #1317