-
Notifications
You must be signed in to change notification settings - Fork 3
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
Stabilize chainHead
to version 1
#147
Conversation
Signed-off-by: Alexandru Vasile <[email protected]>
Signed-off-by: Alexandru Vasile <[email protected]>
Signed-off-by: Alexandru Vasile <[email protected]>
Signed-off-by: Alexandru Vasile <[email protected]>
Signed-off-by: Alexandru Vasile <[email protected]>
Signed-off-by: Alexandru Vasile <[email protected]>
Signed-off-by: Alexandru Vasile <[email protected]>
Signed-off-by: Alexandru Vasile <[email protected]>
Signed-off-by: Alexandru Vasile <[email protected]>
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 to me! We've been using these methods for a while in Subxt and they are roughly at parity with the legacy methods in terms of the functionality exposed.
My stance is that, although there are likely a few changes I'd like to see here, it's much better to stabilise something now rather than get caught up with aiming for perfection and not get anything stabilised for a while.
Once these are stabilised, we can introduce v2 etc methods if needed to accomodate future requests and changes. We can also have confidence that PAPI will Just Work, and work to stabilise the "unstable backend" in Subxt (which relies on these currently unstable methods).
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 PR stabilizes all chainHead methods to version 1.
cc @paritytech/subxt-team @tomaka @josepot