You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deploying a contract using one of the ts wrappers produces redundant code, since the user needs to use a static method of the contract class to create the deployment, and then manually create an instance of that same class. The deployment should just return a Contract instance.
constcontract=awaitZkTokenContract.deploy(aztecRpcServer,100n,owner).send().wait().then(r=>newZkTokenContract(r.contractAddress!,wallet));// Should not be necessary to refer to ZkTokenContract again!
Same goes when using the ContractDeployer:
constdeployer=newContractDeployer(abi,aztecRpcServer);consttx=deployer.deploy().send();awaittx.isMined(0,0.1);constreceipt=awaittx.getReceipt();constcontract=newContract(receipt.contractAddress!,abi,wallet);// Should not be necessary to create an instance manually using the same `abi`!
The text was updated successfully, but these errors were encountered:
Deploying a contract using one of the ts wrappers produces redundant code, since the user needs to use a static method of the contract class to create the deployment, and then manually create an instance of that same class. The deployment should just return a Contract instance.
Same goes when using the ContractDeployer:
The text was updated successfully, but these errors were encountered: