feat(workflow): support TypeInfo on Signal definitions - #2318
Open
THardy98 wants to merge 4 commits into
Open
Conversation
THardy98
marked this pull request as ready for review
August 13, 2026 20:53
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Signal definitions can now provide input
TypeInfo. The SDK applies that information when encoding Client signals, signal-with-start requests, and Workflow-originated external or child signals, and when decoding arguments for Workflow Signal handlers.This is limited to definition-supplied type information. String-named Signal call sites will be addressed separately.
Why?
Signal arguments currently lose application-specific types at payload conversion boundaries. Carrying
TypeInfoon the Signal definition lets callers and handlers consistently apply the same conversion contract.This API is experimental. Existing Signals without type information retain their current conversion behavior, with no rollout or manual steps required.
Checklist
Closes: N/A
How was this tested: Repository build; ESLint and Prettier checks; workspace package lint checks; commit lint; and all 12 focused TypeInfo integration tests, covering Client, signal-with-start, external Workflow, child Workflow, and handler conversion paths.
Any docs updates needed? No; documentation will accompany the completed experimental API.