Context hook for payload visitor#243
Merged
jmaeagle99 merged 1 commit intotemporalio:masterfrom Mar 30, 2026
Merged
Conversation
yuandrew
approved these changes
Mar 30, 2026
| if options.SkipSearchAttributes { continue } | ||
| {{end}} | ||
| if o == nil { continue } | ||
|
|
Contributor
There was a problem hiding this comment.
This only handles payloads, do we want to create a GH issue for a future visitFailures feature for ContextHook? Maybe something worth tracking in the Go SDK as a future feature?
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 changed?
Add optional
VisitPayloadsOptions.ContextHookto allow updating the context on a per-message basis.Why?
Allow contextual information for each proto message instance so that descending payload visiting has access to it. For example, this enables context awareness when visiting the commands of a workflow task completion request.
How did you test it?
Added new tests to validate existing behavior and new behavior.
Potential risks
Low. This setting is marked as experimental and requires opt-in to enable the new behavior. Existing usage should see no behavioral differences.