Repository navigation
Return response metadata through the return annotation - #3
Merged
Merged
Conversation
…of the CallDetails out parameter
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.
Reading response headers and trailers used to go through a
CallDetailsobject passed in asdetails=and filled after the call, which reads like an out parameter and never felt like Python. Now a method annotated-> tuple[T, grapec.Metadata](members in either order,tuple[None, grapec.Metadata]for a thrift void) simply returns that tuple, andCallDetailsis gone. The same wire method can be declared twice under different Python names to get both shapes,export_protodedupes those.