Replies: 3 comments
-
Also seeing this, would love to know the best way to handle it! 🙂 |
Beta Was this translation helpful? Give feedback.
0 replies
-
Curious if you found a viem native solution for this problem? The two things I do right now is either 1. move all custom errors to a single contract and inherit it such that all of the possible errors show up on the calling contracts' ABI. 2. Iterate through all possible ABI's with viem's |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Given you have a contract that calls another contract, sometimes the other contract reverts with a custom error. However, the calling contract does not have that error in it's abi, so viem cannot decode that error result.
Example:
What's the recommend approach to be able to decode errors from the
CalleeContract
when calling it from theCallerContract
usingviem
?Beta Was this translation helpful? Give feedback.
All reactions