fix: json-abi not using anonymous when converting to interface #342
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey so was seeing what would happen if I ran all of the abis ever verified on etherscan through alloy's
solmacro and this was one of the errors I ran into.This error occurs due to the fact that when we go to convert parsed json-abi into a interface for syn-solidity to then parse as a normalization step, the anonymous keyword on events was not getting included into the interface and was causing an error.
Heres an example:
https://etherscan.io/address/0x29c1aaa2e5bd43692f516d9a0c3d2a0f37b59053#code