feat: support ReceiveFunc for client. #73
#205
Closed
Conversation
This file contains 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
|
Thank you for bringing up this requirement. I understand that it can be necessary to define alternate names for hub or receiver functions if the other parties API cannot be changed. Likewise we should not change the API of this package by changing the ReceiverInterface. Please look at #206. Does this serve your needs? BTW I don't think this is the same as #73 and I am still curious how to fulfill #73 in a general way. Maybe with generics? |
|
Thank you for your reply. #206 is my needs. I modified the |
|
Solved by #206 |
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.
Add
ReceiveFuncfor client, use method map in base receiver, to support the methods that cannot be named in Go.