eth_sendTransaction data vs input

[mpetrunic]

Hardhat provider expects data field with eth_sendTransaction API which is inconsistent with the spec.

Expected behavior

For web3.js to work in the hardhat.

Actual behavior

The transaction gets reverted because of the missing data field. Alternatively, we can try to patch the provider in the hardhat-web3 package.

Steps to reproduce the behavior

1. [First step]
2. [Second step]
3. [and so on...]

Logs

Environment

[mpetrunic]

Potential solution, send both input and data

[mpetrunic]

cc @spacesailor24

[mpetrunic]

This is blocking: web3/hardhat#1

[spacesailor24]

Submitting both input and data seems to be fine for both Geth and Ganache. However, getTransaction only returns input for both clients

@mpetrunic @web3/web3-js Should we format the response for getTransaction to return data when only input is present and vice versa, or just leave it as whatever the client returns? One downside of leaving it as is, if a user submits tx.data, they'd probably expect to be able to access data like so: (await getTransaction(txHash)).data

[mpetrunic]

@spacesailor24 I think it's fine to leave only "input" for getTransaction. We have return types (and docs) in place so if user tries to use .data it will get type error.