-
Notifications
You must be signed in to change notification settings - Fork 268
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
Use tokio directly instead of jsonrpc_server_utils's re-export #116
Conversation
Oh nice. That was probably a holdover from when we had to support two versions of tokio 🤕 |
Seems probable ha. That being said, we can likely rip out the dependence on that crate altogether; looks like only other place and it is also reimporting something from tokio |
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
Clarification on this statement added to the summary up top but - We no longer import & use the crate directly, altho we still use the crate indirectly through some of our deps |
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.
thanks!
Summary of Changes
Import objects from tokio directly instead of relying on the re-export from
jsonrpc_server_utils
:https://docs.rs/jsonrpc-server-utils/latest/jsonrpc_server_utils/#reexports
We no longer import & use the crate directly, altho we still use the crate indirectly through some of our deps