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
Hey everyone.
I've encountered an issue where after the multicall, the returnValues prop in the callsReturnContext item is an array (of bignums in my case), instead of an array of objects with key/value pairs.
It's the first time I've encountered such an issue because I've always used this lib for multicalls but it turned out that all of those always had a singular return, meaning that they returned one value and not a collection.
The ABI is correct, I triple checked. Everything works as expected if I call the contract directly.
I'm providing screenshots for context, however, if those are not enough - please let me know, I'll create a codepen demo.
The text was updated successfully, but these errors were encountered:
it's a good feature to add right now it doesn't try to map back to objects it just puts them in tuple order, so [0] = [0] of output but your way does make it nicer to read but would be a breaking change so would have to be in a 3.0.0 version - thanks for suggesting this
Hey everyone.
I've encountered an issue where after the multicall, the returnValues prop in the callsReturnContext item is an array (of bignums in my case), instead of an array of objects with key/value pairs.
It's the first time I've encountered such an issue because I've always used this lib for multicalls but it turned out that all of those always had a singular return, meaning that they returned one value and not a collection.
The ABI is correct, I triple checked. Everything works as expected if I call the contract directly.
I'm providing screenshots for context, however, if those are not enough - please let me know, I'll create a codepen demo.
The text was updated successfully, but these errors were encountered: