Decode uint128 & uint64

[KeKs0r]

Adding Decoding for uint128 and uint64.

[dawsbot]

Hi @KeKs0r , thanks for the PR! Can you provide a test which failed before but succeeds now?

[KeKs0r]

Checking the other tests, those are quite e2e-ish. So directly against chain. And none of the currently included ABIs have those fields. Should I just add a new ABI that I know uses those fields?

[dawsbot]

Checking the other tests, those are quite e2e-ish. So directly against chain. And none of the currently included ABIs have those fields. Should I just add a new ABI that I know uses those fields?

Sure, you're right that I did not design the tests well previously because they are very e2e. If you can rip out and make a focused test with an ABI that includes uint128 & uint64 that would be epic!

[dawsbot]

Hey @KeKs0r I forgot to follow-up here. Was there anything more you needed to get unblocked writing those tests?

Thanks for the PR 🙏

[dawsbot]

Checking the other tests, those are quite e2e-ish. So directly against chain. And none of the currently included ABIs have those fields. Should I just add a new ABI that I know uses those fields?

You're spot on, these tests I've written are not using proper mocking nor proper separation of concerns. I'm doing at-least one step to improve this now with #201

[dawsbot]

I think we're almost ready to solve this.

We can make a test which validates we match encodeFunctionData from ethers: https://docs.ethers.org/v5/api/utils/abi/interface/#Interface--encoding

We currently have this logic all crammed into the other functions but this task should also separate it properly