Extend serialization context to schedule client and workflow client#1997
Draft
Extend serialization context to schedule client and workflow client#1997
Conversation
Wire serialization context through the core workflow, worker, and primary client paths so custom payload and failure converters can see which workflow or activity owns each payload. Add focused tests for the main success and failure boundaries. See tests in test-serialization-context.ts and the workflows it uses in test/src/workflows/serialization-context.ts to see the current boundaries where serialization context is implemented.
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
Extended
SerializationContextusage to the remaining workflow client usages (describe,list), and the schedule client.Note that this PR scoped serialization context support for schedules to schedule start-workflow actions only. It does not include the top-level schedule memo and schedule list interfaces - those payloads belong to the schedule itself and therefore don't clearly map to a workflow or activity context.
Part of [Feature Request] Serialization context for codecs and converters #1661
Extends Add
SerializationContextAPI for core payload/failure conversion paths #1996How was this tested:
Integration tests