UseCallContract response type loses type information for result about starknet-react

[fracek]

The type definition in starknet.js is wrong. The return value is a weird array with keys(!), the objects are deserialized from a flat felt array to their type (so for example balanceOf has one element that is an uint256 struct). I talked with @janek26 about this, and they're open to a PR that adds type safety around contract calls.

[janek26]

please contribute! :-)

[fracek]

I will :)

[fracek]

This is still an issue in v2.

[HumbertoTM10]

Is this available to pick up?

[fracek]

This can be done as part of the work on v3. I will try to organize the effort so you can contribute to it.

[fracek]

Hey @HumbertoTM10 , you can work on this. Make sure to start your work from next-v3 and make the PR against that branch. A good starting point is studying abi wan and see how it works.

[HumbertoTM10]

Hey @fracek, got it! Assign it to me, will work on it!

[fracek]

Done. Make sure to add tests to test types in your PR.

[Pet3ris]

Love it