Roxane Létourneau

Results 63 comments of Roxane Létourneau

In addition to @jevonearth 's comment, we noticed that the `unrecognized operation` message is displayed when we are working with smart contracts (deploy and calling a method).

Closing because we have the script "originate-known-contracts.ts" in the integration test folder to deploy the contracts used in the integration tests. We don't need a duplicated script in the examples...

Hey team! Please [add your planning poker estimate](https://app.zenhub.com/workspaces/Taquito-Development-Team-60ca841c87ca580010057707/issues/ecadlabs/taquito/1888?planning-poker) with Zenhub @dsawali @hui-an-yang @zainen

> packages/taquito-sapling/saplingOutputParams.js and packages/taquito-sapling/saplingSpendParams.js should not be committed. There are in the gitignore, I am not sure why they ended up here. @michaelkernaghan

@johnnyshankman We provide two syntaxes for the batches: - using chained methods `withTransfer`, `withOrigination`, `withDelegation`, ... - or using an array of `ParamsWithKind` The `EstimationProvider` only supports the second syntax....

We have a script to deploy the known contracts in the integration tests folder: https://github.com/ecadlabs/taquito/blob/master/integration-tests/originate-known-contracts.ts And one in the example folder: https://github.com/ecadlabs/taquito/blob/master/example/deploy-integration-tests-contracts.ts We can delete the one in the example...

Hi @RomarQ, I have a question regarding this request. I know that we expose the operation results before the first confirmation on the contract API side. We can do that...

Ok I see, having the address of the originated contract before the confirmation is interesting. But the thing with the wallet API is that we are missing information that would...

Hey team! Please [add your planning poker estimate](https://app.zenhub.com/workspaces/Taquito-Development-Team-60ca841c87ca580010057707/issues/ecadlabs/taquito/1872?planning-poker) with Zenhub @dsawali @hui-an-yang @zainen

@danielelisi Can you confirm what was the `pollingIntervalMilliseconds` used? I ran the integration tests suite against a Tezos sandbox network with minimal_block_delay set to 1 second. I configured the TezosToolkit...