Open
Conversation
when user use custom channel implement, for example a dynamic channel, which can connect multi endpoints, and call ban method to ban the bad endpoints when rpc call is failed, with this PR user now can access the inner field
Sherlock-Holo
force-pushed
the
client-inner-getter
branch
from
4a11d74 to
44b97d5
Compare
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.
Motivation
when user use custom channel implement, for example a dynamic channel, which can connect multi endpoints, and call
banmethod to ban the bad endpoints when rpc call is failed, with this PR user now can access the inner fieldSolution
add the getter methods to allow user access the inner field