-
-
Notifications
You must be signed in to change notification settings - Fork 266
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
Process chain segment #1934
Process chain segment #1934
Conversation
Code Climate has analyzed commit 0cdc0e9 and detected 1 issue on this pull request. Here's the issue category breakdown:
View more on Code Climate. |
@@ -105,4 +112,8 @@ export interface IBeaconChain { | |||
* Pre-process and run the per slot state transition function | |||
*/ | |||
receiveBlock(signedBlock: SignedBeaconBlock, trusted?: boolean): Promise<void>; |
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.
Can we change this to return void
so it's not misleading? the behaviour is very different to processChainSegment
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'd say yes
, would like @wemeetagain to confirm through. I can to create a separate PR if we want to do that.
at least what I see is the name receive*
vs. process*
is the main difference between these 2 apis.
resolves #1772
chain.processChainSegment()
to process a linear chain until completedchain.processChainSegment()
, removed its own processor