Hey Yo!
Hey Yo!
> JsonRpcProvider extends BaseProvider and BaseProvider extends ethers.providers.Provider. So a type that accepts ethers.providers.Provider should be happy with JsonRpcProvider. > > It is possible that there is an ethers version...
I can't even use it, it gives error after few reads of account info
Noticed varying type conflicts in the `useContractCall(s)` methods too
> @ItsShadowl We have implementation of CustomErrors, working with Hardhat - please take a look into the tests in action here https://github.com/TrueFiEng/Waffle/blob/12c2d7209a310202e8b03862972a88735e5803a0/waffle-hardhat/test/reverted.test.ts#L37 The error args and errorName can't be pulled...
> @ItsShadowl Ah sorry I confused UseDapp with Waffle because I switch from one to another during the day 🤦♂️ I did notice that, LOL
That's happens with Kovan, it just throws exception without the error message
https://github.com/openethereum/parity-ethereum/issues/10147#issuecomment-462177568 Your exception is probably a kovan exception, which I think might be caused by trying to transfer zero(0) token, so amount should be anything above zero(0). Kovan doesn't go...
Why not just add the `originalError` as sent by ethers.js? That would help others a lot, myself included. The `originalError` will help this draft(#907) too.
the big numbers was an issue with parseFloat, Number and parseInt in Javascript.... Only using Big Number libraries can solve that
> hardhat-chai-matchers should be preferred over Waffle nowadays. I believe both supports Custom Errors, and the implementation can be tested with either. We use Custom Error all over our codebase...