The message execution functions allow to skip dry running (i.e., to skip executing the call in the RPC node first in order to determine the actual gas usage).
This is not the case for the contract deployment functions: they always dry run first in order to estimate gas.
In certain scenarios it is useful to skip dry running also for contract deployment, e.g., in order to analyze an error that happens during deployment.
TODO
add the optional Boolean flag skipDryRunning to the deployContract function, if it is true, then don't dry run but use the provided gas limits as the gas limits to the actual execution
The message execution functions allow to skip dry running (i.e., to skip executing the call in the RPC node first in order to determine the actual gas usage).
This is not the case for the contract deployment functions: they always dry run first in order to estimate gas.
In certain scenarios it is useful to skip dry running also for contract deployment, e.g., in order to analyze an error that happens during deployment.
TODO
skipDryRunningto thedeployContractfunction, if it istrue, then don't dry run but use the provided gas limits as the gas limits to the actual execution