-
Notifications
You must be signed in to change notification settings - Fork 15
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
Upgrade to near-sdk-rs 4.1 and test functionality #23
Comments
I would like to work on this one |
I had to revert #26 (see 8fc1fdd) due to #26 (comment). |
Hi @frol – Can you please provide an update on this ticket? What's the next step here? Do we need to reassign or change the status? |
It seems that @gautamprikshit1 did not have time to proceed with this issue, so I unassigned him, and if someone is ready to jump on it, learn more in #26 (comment) |
Hi @frol, what is pending in this issue atm? |
@jaswinder6991 well, by this time it will be easier to start the PR from scratch (just manually port the changes) as rebasing will probably just make things unnecessarily complicated. |
With #46 merged, this issue is unblocked, though I think that instead of trying to rebase #26, it would be easier to re-apply the changes manually. cc @jaswinder6991 |
I'm going to take a look at this. |
@PiVortex The expected value is correct, the |
Resolved in #63. |
Problem
Currently DevHub contract is using near-sdk-rs 3.x. Several API enhancements have been introduced in 4.0 and security updates will also only update for 4.x so we should update to use near-sdk-rs 4.1.
User Story
As a developer, I want to use near-sdk-rs 4.x APIs in develop DevHub contract. Particularly I would like to use
require!
macro and new cross contract API.Acceptance Criteria
Near.call
andNear.view
.if ... panic
torequire!
The text was updated successfully, but these errors were encountered: