-
Notifications
You must be signed in to change notification settings - Fork 5
feat: improve rpc namespace #454
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
Conversation
CodSpeed Performance ReportMerging #454 will not alter performanceComparing Summary
|
frisitano
left a comment
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. Can you search the repository for places where we have hard-coded use of rollupNode_ namespace for rpc and replace with the correct namespace? I know that there will be some cases in the sequencer-migration directory, but there may be other places as well.
All of the name of rpc methods remain unchanged. they still use |
#[rpc(server, client, namespace = "rollupNodeAdmin")]
pub trait RollupNodeAdminApi {
/// Enables automatic sequencing in the rollup node.
#[method(name = "enableAutomaticSequencing")]
async fn enable_automatic_sequencing(&self) -> RpcResult<bool>;
/// Disables automatic sequencing in the rollup node.
#[method(name = "disableAutomaticSequencing")]
async fn disable_automatic_sequencing(&self) -> RpcResult<bool>;
}But didn't you put these methods in the admin namespace? |
Oh, sorry, my mistake. yeah, will update all |
This PR separate rollupNode rpc methods. the basic rpc methods
rollupNode_status,rollupNode_getL1MessageByIndexandrollupNode_getL1MessageByKeyare put in namespace rollup_node, enabled by default. The admin methodsrollupNode_enableAutomaticSequencingandrollupNode_disableAutomaticSequencingare moved to namespace rollup_node_admin, and requires manual enablement.corresponding issue: #445