-
Notifications
You must be signed in to change notification settings - Fork 87
WEB3-513: contracts: dependency cleanups #654
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
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.
Looks good overall. Thank you for working taking care of this.
/// Re-export of [alloy], provided to ensure that the correct version of the types used in the | ||
/// public API are available in case multiple versions of [alloy] are in use. | ||
/// | ||
/// Because [alloy] is a v0.x crate, it is not covered under the semver policy of this crate. | ||
pub use alloy; | ||
|
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 don't think we should remove this, because it might break downstream users and I think this is actually still helpful.
I like the idea of bringing in |
SetVerifierService
behind featurealloy
has been released in v1, so there is no immediate need anymore to expose it