-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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: forge selectors
feature request meta issue
#5012
Comments
Thanks for opening this @lmanini. I'll defer to @mattsse and @Evalir but in the interest of keeping PRs easy to review/test, my suggestion would be as follows: The first PR just structures things:
Then follow up PRs for:
(Also I think |
Is there an example of how this should be handled? I was thinking of just doing a |
Line 168 in cae66aa
|
oh ok haha - just started off with rust, still got a long way to go |
Marking as resolved by #5116 + #6205 Now yields:
|
Component
Forge
Describe the feature you would like
Main feature I'd like to add is a cmd to check for colliding method selectors between two given contracts.
@mds1 suggested to implement a
forge selectors
cmd and have the following initial subcommands:forge selector collision
for what my original PR doesforge selector list <options>
to list function selectors and/or error selectors and/or event sigs for certain/all files in a projectforge selector upload
to replaceforge upload-selectors
Additional context
context: #4973
The text was updated successfully, but these errors were encountered: