feat: add metadataCallback to CallOptions - #9298
Merged
Merged
Conversation
Hectorhammett
force-pushed
the
add-metadata-callback-support
branch
3 times, most recently
from
June 24, 2026 20:21
b719471 to
bfc6fb4
Compare
Hectorhammett
force-pushed
the
add-metadata-callback-support
branch
from
July 6, 2026 19:53
bfc6fb4 to
f3f0f0c
Compare
bshaffer
approved these changes
Jul 6, 2026
bshaffer
enabled auto-merge (squash)
July 6, 2026 20:13
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
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.
Currently there is no way to get the response headers in an simple way from the user's perspective:
The gRPC transport supports the
metadataCallbackcallback. This PR allows the user to pass this callback to theCallOptionsso the headers are easily accessible: