Expose encodeFunctionData and decodeFunctionResult as properties on the contract method

[cosullivan]

Describe the Feature

I have some scenarios were I need to call encodeFunctionData() and decodeFunctionResult() and whilst I can do this via the Interface, it would be nice to expose these as properties on the method just like there is;

testContract.testMethod.staticCall(...)
testContract.testMethod.estimateGas(...)

it would be nice to have these;

testContract.testMethod.encodeFunctionData(...)
testContract.testMethod.decodeFunctionResult(...)

The code pretty much exists already in the buildWrappedMethod function.

Code Example

No response

[ricmoo]

That is one of the reasons for moving the buckets from the contract to the methods in v6, so it can be backwards compatible to add new buckets.

I’ll research this a bit to see what all makes sense to add; it might make sense to add the decode to the events too.