-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
chore(rpc): move EthApi
trait into own crate
#8847
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.
supportive
I want to keep changes in other crates minimal and I think we can prevent this by doing re-exports from reth-rpc
@@ -1,6 +1,6 @@ | |||
use crate::primitives::U256; | |||
use clap::Args; | |||
use reth_rpc::eth::gas_oracle::GasPriceOracleConfig; | |||
use reth_rpc_eth_api::GasPriceOracleConfig; |
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.
I want to avoid these changes, instead this should be re-exported from reth-rpc
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.
eth
is the only reth-rpc
module used in reth-node-core
builder, hence why I went with updating the dep here
27ae884
to
c5f6c5a
Compare
4c923b0
to
9ecf026
Compare
incremental progress committed in #8887 |
Moves
EthApi
trait, and building-block traits, into own crate. This makes it possible to implEthApiServer
for a generic type that impl the building-block traits.This way, small parts of the
EthApiServer
impl, can be customised, by overriding the default impl of any of the building-block traits.