Type improvement : <contract>.functions could be ContractFunctions<ContractTransaction>

this line https://github.com/ethers-io/ethers.js/blob/e0b1d0e1e0280af860aaa593744a1a177f828397/packages/contracts/src.ts/index.ts#L581

could be readonly functions: { [ name: string ]: ContractFunction<ContractTransaction> };

or am I missing something ?

[ricmoo]

There is no read-only or write-only buckets. All buckets have all functions, including the root. The buckets just change how those methods operate. For any given method all these operations have cases that a given bucket is useful.

• function: for constant, calls it, otherwise signs and sends a transaction
• populateTransaction: for a constant, the TX w/ data required for eth_call, otherwise the transaction required to send
• estimateGas: for constant, the gas consumed executing this on a node, otherwise the gas limit estimated for the network to accept it
• callStatic: for constant functions, it does nothing different than the root, otherwise use eth_call instead of sending a transaction
• root: same as function but with single argument functions reduced to their value

If you ever needed just the read-only, you could use contract.interface.functions.filter(f => f.constant) and if you wanted state-changing contract.interface.functions.filter(f => !f.constant). Or you could find only payable or only non-payable or only pure… Whatever category you wanted. But those cases are not common, so I don’t see a need for a short-cut. 😃

For a somewhat more complete explanation, see here although it could certainly use more examples…

[ricmoo]

I think the OP has been answered, so I’m going to close this now. Please feel free to re-open if I’m mistaken though.

Thanks! 😃