We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
on last viem versions (2.9.25+) e.details contains the whole error message
e.details
scaffold-eth/se-2-challenges#174 (comment)
although I didn't find in their changelog what could cause it.
I fixed a problem for now by locking viem to 2.8.16 but looks like we need to rewrite getParsedError a bit.
viem
2.8.16
getParsedError
Opening an issue here since in main se-2 we have yarn.lock.
yarn.lock
Probably I'm missing something, you can check it here sre challenge 1 wagmi 2 backmerge
1df6640 - normal error messages
c5f95cc - broken error messages
The text was updated successfully, but these errors were encountered:
Fixed at scaffold-eth#849 (comment) 🙌
Sorry, something went wrong.
No branches or pull requests
on last viem versions (2.9.25+)
e.details
contains the whole error messagescaffold-eth/se-2-challenges#174 (comment)
although I didn't find in their changelog what could cause it.
I fixed a problem for now by locking
viem
to2.8.16
but looks like we need to rewritegetParsedError
a bit.Opening an issue here since in main se-2 we have
yarn.lock
.Probably I'm missing something, you can check it here sre challenge 1 wagmi 2 backmerge
1df6640 - normal error messages
c5f95cc - broken error messages
The text was updated successfully, but these errors were encountered: