Skip to content
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

feat: patch account and access keys added #122

Conversation

Buckram123
Copy link

Trying to implement #19. Not sure, how to make a friendly API for this. Thinking of using builder here.

Copy link
Member

@ChaoticTempest ChaoticTempest left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks so much for implementing this! Just some minor things to add

Comment on lines +194 to +198
account_id: &AccountId,
amount: Option<Balance>,
locked: Option<Balance>,
code_hash: Option<CryptoHash>,
storage_usage: Option<StorageUsage>,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure, how to make a friendly API for this. Thinking of using builder here.

yeah definitely, would be great if we can get a builder going for this. You can take a look at patch.rs to see how to get one going. Probably also best to put it there as well

@@ -158,6 +162,70 @@ impl Sandbox {
Ok(())
}

pub(crate) async fn patch_account(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add tests for this and patch_access_key. Let me know if they aren't as straightforward to implement, but they should be simple if you follow the ones in tests/patch_state.rs.

@Buckram123
Copy link
Author

Closing in favor of #124.

@Buckram123 Buckram123 closed this Apr 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants