-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
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
forge inspect <contract> errors/events
#3142
Comments
+1
One reason is this bug in the invariants: #4178 |
In the meantime, you can use $ cast sig "transfer(address,uint256)"
# Outputs 0xa9059cbb
$ cast sig "Unauthorized(address)"
# Outputs 0x8e4a23d6 |
Yeah, I know, but have to manually do it for all the errors in my contract, which is not hard, but's annoying af |
think this can be closed, |
That's amazing, thanks for the heads-up @grandizzy! |
@grandizzy That's awesome - could you link to the PR for the feature? This should also solve this: #3656 . Thank you. |
here it is #5228 |
@mattsse this one can be closed |
Component
Forge
Describe the feature you would like
When working with custom errors, sometimes for whatever reason the chain will spit out the raw bytes instead of the parsed error.
In those cases, it'd be very useful to be able to list the
bytes4
sig of all the errors a contract may throw so then I can parse the raw bytes with cast.I think that for completeness, I'd do the same for events, which would be useful when sometimes, even if the contract is verified, etherscan shows the raw byes.
Thanks!
Additional context
No response
The text was updated successfully, but these errors were encountered: