PLEASE PROVIDE SENSIBLE ERRORS

[beether]

"Invalid number of solidity arguments" is AIDS.

You have the freaking ABI that defines which inputs are expected, their order, and their type. Why such a miserable error message? FFS... it's so unnecessarily difficult to debug this error, especially since you (rather idiotically) try to infer the different inputs (which CAN be objects) from the transaction options (which IS an object).

It infuriates me, and countless others.

JUST FREAKING FIX THIS. LET ME PASS AN ARRAY OF INPUTS.

[Andromelus]

Your demand might be legit, but the way you demand it is not. They work for you, at least respect it.

[frozeman]

:)
In 1.0 there is no transaction object anymore.
And yes the error could be more concise, and as this is an open source projects youre welcome to make the change, PR and we discuss ;)

[beether]

So, in other words, it's not a priority to fix this, even though pretty much all dApp developers need to target MetaMask, which uses v0.2.x. v1 is great and I love the design and can't wait to use it... but It's really annoying that you don't seem to care about making actual development easier, and quite telling that your response is "it's open source, take it or leave it"

On an unrelated note, v1 could have been made to wrap 0.2.x, allowing it to be backward compatible, and allowing everyone in the world to immediately use it with MetaMask. Not a priority, I suppose.

[beether]

@Andromelus what do you mean "they work for you"?

[nick]

@beether you can use v1 with MetaMask https://guillaumeduveau.com/en/blockchain/ethereum/metamask-web3

[nivida]

@beether I will implement the Winston logger for a better and consistent error handling.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions