-
Notifications
You must be signed in to change notification settings - Fork 6
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
Add support for sapphire-paratime 2.x #16
base: master
Are you sure you want to change the base?
Conversation
e1f11cf
to
536f5af
Compare
536f5af
to
746a641
Compare
7b94b2d
to
296b961
Compare
frontend/package.json
Outdated
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 think this can just point now to ^0.2.11
and ^2.0.1
as the mentioned issues are merged
type Provider, | ||
type Signer, | ||
toBeHex, | ||
toBeHex, toUtf8Bytes, |
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.
toBeHex, toUtf8Bytes, | |
toBeHex, | |
toUtf8Bytes, |
This PR should be now merged in the vue branch. |
1241376
to
34d471c
Compare
34d471c
to
11c2ae8
Compare
11c2ae8
to
3b27751
Compare
This would break, current React rewrite, as it is based on "v1". Can we hold off merging? Until rewrite of frontend is done on top of this PR? cc: @matevz |
This PR:
Merge after oasisprotocol/sapphire-paratime#332 and oasisprotocol/sapphire-paratime#303