-
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
reexport relevant crates from op-reth
#11493
Comments
reasonable |
do you want to take this? |
Yep, I'm on it! Thanks! |
@mattsse Do you think it's wise to have pub use reth::*; in lib.rs? Essentially this would mean the pub mod optimism_payload {
pub use reth_optimism_payload_builder::*;
} It also means you get non-optimism specific code reexported from |
Additionally, how do you feel about reexporting all of the alloy/op-alloy types from reth/op-reth respectively? users could use like this: use reth::alloy::rpc_types::*;
use op_reth::op_alloy::rpc_types::*; This would be pretty nice as it would prevent consumers from having to respecify all their alloy dependencies in their tomls (and having to match versions). |
Describe the feature
The
reth
crate reexports all/most of it's dependencies from alib.rs
. For users building onop-reth
the same could be useful.I'd be happy to submit a PR if it would be welcome!
The text was updated successfully, but these errors were encountered: