Add JSON-RPC metadata provider#63
Open
calebnorman wants to merge 1 commit into
Open
Conversation
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.
Summary
setGlobalMetaProvideras a public SDK API_metafieldWhy
Consumers sometimes need to attach cross-cutting request metadata, such as trace context, without monkey-patching transports or forking protocol internals.
Use case
User's app wants to propegate OpenTelemetry spans for dispatch/session turns. This hook lets them inject W3C
traceparent/tracestateinto SDK JSON-RPC requests so daemon-side work can join the same trace in observability providers, instead of appearing as a separate trace.Verification
npm run typechecknpx vitest run tests/protocol.test.ts tests/public-api.test.ts