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

chore: update workspaces to 0.3 #789

Merged
merged 8 commits into from
May 12, 2022
Merged

chore: update workspaces to 0.3 #789

merged 8 commits into from
May 12, 2022

Conversation

austinabell
Copy link
Contributor

WIP since test is broken

@itegulov
Copy link
Contributor

I left some TODOs in nft and ft examples that should now be resolvable with workspaces 0.2. You could tackle them in this PR or I can do it in a follow up PR, up to you

@austinabell austinabell marked this pull request as ready for review May 11, 2022 14:43
@austinabell
Copy link
Contributor Author

I left some TODOs in nft and ft examples that should now be resolvable with workspaces 0.2. You could tackle them in this PR or I can do it in a follow up PR, up to you

I'll separate that change since this is blocking #742

@austinabell austinabell changed the title chore: update workspaces to 0.2 chore: update workspaces to 0.3 May 11, 2022
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.

minor nit but overall looking good

@@ -27,25 +27,25 @@ async fn init(
initial_balance: U128,
) -> anyhow::Result<(Contract, Account, Contract)> {
let ft_contract =
worker.dev_deploy(include_bytes!("../res/fungible_token.wasm").to_vec()).await?;
worker.dev_deploy(&include_bytes!("../res/fungible_token.wasm").to_vec()).await?;
Copy link
Member

Choose a reason for hiding this comment

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

looks like you forgot to clean some of these up:

Suggested change
worker.dev_deploy(&include_bytes!("../res/fungible_token.wasm").to_vec()).await?;
worker.dev_deploy(include_bytes!("../res/fungible_token.wasm")).await?;

Comment on lines 86 to +90
let wasm = fs::read("res/callback_results.wasm").await?;

let worker = workspaces::sandbox();
let worker = workspaces::sandbox().await?;

let contract = worker.dev_deploy(wasm).await?;
let contract = worker.dev_deploy(&wasm).await?;
Copy link
Contributor

Choose a reason for hiding this comment

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

any reason not to use include_bytes! here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

tried to keep this change unopinionated, can follow with that change in another

@austinabell austinabell merged commit bc88d7e into master May 12, 2022
@austinabell austinabell deleted the austin/workspaces_02 branch May 12, 2022 01:22
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.

3 participants