-
Notifications
You must be signed in to change notification settings - Fork 266
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
refactor: renaming abi as artifact #2756
Conversation
df2f9a1
to
863ba94
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't look like anything's changed here, still see ABI on the copy if that was the intention
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are right. Updated the diagram in 3a56231
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to keep the directory as foundation/abi
if all other references related to this are now called artifact
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would rename it but I think it makes sense to do it in a separate PR because moving files and renaming their contents can result in ugly conflicts.
Fixes #2101
Note: In some places it made sense to use the ABI term because it really referred to what ABI means in the Ethereum world (function name, args, return types and no bytecode and verification key). Given this I renamed
FunctionAbiHeader
asFunctionAbi
and what wasFunctionAbi
is nowFunctionArtifact
.Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.