You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I expect this piece of code to work accordingly to types defined.
As it stands first call in multicall should return type [bigint, bigint]. Unfortunately, after upgrading to 0.3.12 in order to fix incorrect peer deps in wagmi@next, this piece of code throws an error. Bumping back to 0.2.8 fixes it.
This issue has been locked since it has been closed for more than 14 days.
If you found a concrete bug or regression related to it, please open a new bug report with a reproduction against the latest Viem version. If you have any questions or comments you can create a new discussion thread.
Is there an existing issue for this?
Package Version
0.2.8 and 0.3.12
Current Behavior
I expect this piece of code to work accordingly to types defined.
As it stands first call in multicall should return type [bigint, bigint]. Unfortunately, after upgrading to 0.3.12 in order to fix incorrect peer deps in wagmi@next, this piece of code throws an error. Bumping back to 0.2.8 fixes it.
Here's the error message:
Expected Behavior
I expect the piece of code mentioned above return proper multicall results.
Steps To Reproduce
I reckon you can reproduce by making a multicall in which one of calls returns an array of fixed number of elements
Link to Minimal Reproducible Example (StackBlitz, CodeSandbox, GitHub repo etc.)
No response
Anything else?
I think it's related to #398
Types are displayed correctly
I can do a minimal example, but in the nearest future
The text was updated successfully, but these errors were encountered: