Flip the contract function calls

• Version: 4

What was wrong?

The order of calls (contract.call().doSomething()) could be more intuitive.

How can it be fixed?

Basic Approach

web3.js seems to have a solid solution: contract.functions.method().call()

Plus:

• ..method().transact()
• ..method().estimateGas()
• etc

This API can coexist alongside the old way of calling contract methods.

API Naming

functions is a little long, here are some other options:

• contract.api.doSomething().call()
• contract.public.doSomething().call()
• contract.build.doSomething().call()
• contract.make.doSomething().call()
• contract.prep.doSomething().call()
• contract.useabi.doSomething().call()
• contract.go.doSomething().call()
• contract.methods.doSomething().call() Added

Also, think about how the name will sound when used with other execution options, like transact, estimateGas, and buildTransaction

Requirements

• add new API
• document new API in docs/
• add deprecation warning to old call/transact/etc methods
• Bonus: Update ConciseContract to use the new Contract API under the hood (with no change to the external API)

[dylanjw]

Is anyone working on this? If not, I would like to give it a try.

[gitcoinbot]

This issue now has a funding of 0.335 ETH (110.39 USDT) attached to it. To view or claim this funding, click here.