-
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
feat: EngineApiBuilder
#14354
feat: EngineApiBuilder
#14354
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.
lgtm. makes sense imo to double this up in op-alloy and just change result type to RpcResult
to derive jsonrpsee to close #14211
pub struct BasicEngineApiBuilder<EV> { | ||
engine_validator_builder: EV, | ||
} |
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.
pub struct BasicEngineApiBuilder<EV> { | |
engine_validator_builder: EV, | |
} | |
pub struct BasicEngineApiBuilder<EB> { | |
engine_api_builder: EB, | |
} |
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.
this is an engine_validator_builder
as it provides EngineValidator
to pass here
validator: Validator, |
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.
hm then can the struct name change to BasicEngineValidatorBuilder
?
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.
ah I see this pr also aggregates the validator api and the regular api into one type. docs could be more helpful in reflecting this design choice.
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.
cool
Towards #13831
Add
EngineApiBuilder
toRpcAddOns
which uses defaultEngineApi
impl by default but already can be customized to use any implementation.Technically this is all we need for #13831 but I think we can keep it open until we have at least one usecase for custom engine API implemented (either OP or custom header example)