-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Option to ignore warnings from dependencies in foundry.toml #1200
Comments
I can take this? |
sure! lmk if you need some pointers, happy to take a look where we can get that info |
@mattsse of course, thanks |
Hello guys I tried to replicate your issue but I couldn't. Could you share exactly what I do? |
@Alef-gabriel To replicate this problem, try this project. It should raise several warnings:
|
@guidanoli Did you find any solution to this? |
@loocapro perhaps you want to take this? I believe this can be solved with:
The current workflow wrt to ignored errors is: foundry/crates/config/src/lib.rs Line 636 in 00cec1d
I think we want to enhance that setting to also make it possible to ignore paths |
but for this specific error @wottpal you can silence this via:
|
Great, that already removes a lot of warnings when having ens contracts as a dependency in But some are still persisting:
And ofc I could just ignore the specific error code, but actually I would like to get those for all files under |
here's a list of supported aliases: foundry/crates/config/src/error.rs Lines 202 to 214 in 00cec1d
but the error code works as well |
Sure, I can take it! |
[Related to #1200](foundry-rs/foundry#1200) --------- Co-authored-by: Matthias Seitz <matthias.seitz@outlook.de>
this is now supported via new config setting will add to book |
Component
Forge
Describe the feature you would like
Some of my projects have dependencies I can't change. Due to implementations of some of the abstract contracts, there are unused imports that cause warnings. These warnings spam my stdout and aren't relevant to my projects. I'd like the ability to silence warnings from dependencies.
Additional context
No response
The text was updated successfully, but these errors were encountered: