Use proxy.SystemNexusOperations for nested payload decoding#1068
Closed
chaptersix wants to merge 11 commits into
Closed
Use proxy.SystemNexusOperations for nested payload decoding#1068chaptersix wants to merge 11 commits into
chaptersix wants to merge 11 commits into
Conversation
Replace the CLI's local systemNexusOps registry with the canonical proxy.SystemNexusOperations from go.temporal.io/api. Decode nested payloads in the human-readable display path only, preserving -o json output for SDK replay compatibility.
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.
Summary
systemNexusOpsregistry withproxy.SystemNexusOperationsfromgo.temporal.io/api-o jsonoutput unchanged for SDK replay compatibilityPayloadCodeconcliext.ClientOptionsBuilderso the CLI can pass the codec to the display-path decoderDepends on temporalio/api-go#281
Test plan