feat(workflow): support TypeInfo for client-started workflows - #2252
Merged
Conversation
This was referenced Jul 23, 2026
THardy98
force-pushed
the
feat/ts-type-hints-mapper
branch
from
July 23, 2026 17:06
c1982de to
8c124a3
Compare
THardy98
force-pushed
the
feat/ts-type-hints-workflow-client
branch
from
July 23, 2026 17:06
fa13326 to
fd11f11
Compare
THardy98
force-pushed
the
feat/ts-type-hints-mapper
branch
from
July 23, 2026 17:29
8c124a3 to
b7eb29b
Compare
THardy98
force-pushed
the
feat/ts-type-hints-workflow-client
branch
from
July 23, 2026 17:29
fd11f11 to
d8e2f2e
Compare
THardy98
force-pushed
the
feat/ts-type-hints-mapper
branch
from
July 23, 2026 18:42
b7eb29b to
d655488
Compare
THardy98
force-pushed
the
feat/ts-type-hints-workflow-client
branch
from
July 23, 2026 18:42
d8e2f2e to
28b503e
Compare
THardy98
force-pushed
the
feat/ts-type-hints-mapper
branch
from
July 23, 2026 19:38
d655488 to
f6577e8
Compare
THardy98
force-pushed
the
feat/ts-type-hints-workflow-client
branch
from
July 23, 2026 19:40
28b503e to
68c9a75
Compare
THardy98
force-pushed
the
feat/ts-type-hints-mapper
branch
from
July 24, 2026 16:47
f6577e8 to
eb968c5
Compare
THardy98
force-pushed
the
feat/ts-type-hints-workflow-client
branch
from
July 24, 2026 16:52
68c9a75 to
fa07e89
Compare
THardy98
force-pushed
the
feat/ts-type-hints-mapper
branch
2 times, most recently
from
July 31, 2026 01:21
4152cfb to
d9e55da
Compare
THardy98
marked this pull request as ready for review
August 5, 2026 13:24
THardy98
force-pushed
the
feat/ts-type-hints-workflow-client
branch
from
August 5, 2026 16:26
fa07e89 to
74dfbd7
Compare
chris-olszewski
approved these changes
Aug 7, 2026
|
|
||
| ### Added | ||
|
|
||
| - **Experimental**: Added `TypeInfo` and `TransferTypeConverter` to `@temporalio/common` for converting |
Member
There was a problem hiding this comment.
I think this might need a new section now that 1.22 has been released
THardy98
force-pushed
the
feat/ts-type-hints-workflow-client
branch
from
August 10, 2026 16:29
4d14dd1 to
b029835
Compare
THardy98
force-pushed
the
feat/ts-type-hints-workflow-client
branch
from
August 10, 2026 16:46
b029835 to
da45938
Compare
THardy98
enabled auto-merge (squash)
August 10, 2026 16:46
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
2 participants
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
Added
PayloadTypeInfoanddefineWorkflowOptionsmetadata for client-started Workflows. Workflow functions use definition metadata, while string Workflow types can supply metadata at the call site; start, execute, result, detached-handle, signal-with-start, and update-with-start paths carry it through conversion.This is PR 3 of the stack and depends on #2251. Workflow-internal transitions follow in #2248.
Why?
Workflow input TypeInfo must be available before arguments are decoded in the Workflow isolate. Definition-time metadata provides it for typed function references while preserving a call-site option for string Workflow types.
Workflows without TypeInfo are unchanged. Providing call-site metadata with a Workflow function is rejected to avoid conflicting sources; no rollout or manual steps are required.
Checklist
Closes: N/A
How was this tested: Common, Client, Worker, Workflow, and test package builds; ESLint; Prettier; 10 focused unit tests; and eight mapper-only JSON integration scenarios.
Any docs updates needed? No; documentation will accompany the completed experimental API.