-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(rpc): initial impl #616
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
API looks exactly correct, nice work! I'll let someone else comment on the actual go implementation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could we add some tests? maybe check that success/timeout work correctly?
@bcherry we don't check if someone tries to create a new RpcError with a built-in code, should that be handled? If not, exposing the method for using builtIn codes to create an RpcError could be useful. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm 👍
Thanks @paulwe, will merge this after adding some tests! |
TODO:
- documentation/commentsDone- default timeout valueDone