-
Notifications
You must be signed in to change notification settings - Fork 26
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
Release 1.4.0 - Support of ink! 3.0.0-rc10 #78
Conversation
516c726
to
c5aefe8
Compare
You also will be useful to check that PR: https://github.com/Supercolony-net/openbrush-contracts/pull/49/files |
After rc7 we don't need to support generation for two kind of the code.
This reverts commit 37a244b.
6a27836
to
30c8ed3
Compare
Okay, I'm leaving it as it is. |
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 work! left a couple of comments.
CI is still broken we need a right version of redspot and image with node. Locally all tests are passed.
Updated the code to use references in `Mapping`. Increased the time for integration tests.
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 work!
After fixing of:
use-ink/ink#1131
use-ink/ink#982
use-ink/ink#1145
We are able to use the latest ink! =) At the moment it points to
master
, but then the3.0.0-rc10
release will be ready we will point on it.Updated contract to be compatible with latest
contract-pallet
.Simplified the brush's codegen, now we don't need to worry about the
ink-as-dependency
feature.Of course, reduction of the size of the code!=) All contracts are moved to use
Mapping
instead ofStorageHashMap
. All values are passed by reference instead of move.At the moment only
substrate-contracts-node
works correctly with the latest ink, so integration tests take a lot of time.Most of the documentation is updated, but not all. We will update it fully in follow-up PR.