-
Notifications
You must be signed in to change notification settings - Fork 653
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
refactor(jsonrpc): Structured errors from other JSON-RPC methods #4213
refactor(jsonrpc): Structured errors from other JSON-RPC methods #4213
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.
Great job! Just a few notes on where we can improve even further.
2097b89
to
d116b09
Compare
d4e26e0
to
ebe9e41
Compare
81a2969
to
8b93f62
Compare
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.
Yay! 🎉
We did it! (For those who follows this: this is the last PR in the series of internal JSON RPC error handling refactoring, and the next step would be to expose those errors through JSON RPC with exhaustive and easy-to-reason error kinds)
@bowenwang1996 your review is required, FYI |
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.
Please run nayduck to make sure that there is no regression
@bowenwang1996 does it look ok http://nayduck.eastus.cloudapp.azure.com:3000/#/run/1521 ? |
…ssage, replace parse_error in jsonrpc handler with serialization_error
… are used only under it
…String. Move all experimental json rpc methods to the end of the list
368c9c4
to
d54eb0f
Compare
…nrpc-rest-methods
status
health
EXPERIMENTAL_changes_in_block
EXPERIMENTAL_changes
EXPERIMENTAL_light_client_proof
EXPERIMENTAL_validators_ordered
light_client_proof