-
Notifications
You must be signed in to change notification settings - Fork 991
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
Feature/warnings quiet #13706
Feature/warnings quiet #13706
Conversation
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 only have one UX question:
I'm wondering if we're going to reuse some "id"s in the future, seeing how general the proposed deprecated
one is. If so, maybe it's not warn_id
but warn_category
/warn_tag
or the likes?
I initially implemented some kind of abstract ID, like W01, but then I realized that it was only adding an unnecessary abstraction, and too much boilerplate in code, translating codes back an forth. So I'd prefer to have something with a bit of semantics. We can discuss if we want |
Changelog: Feature: Introduce new
core:skip_warns
configuration to be able to silence some warnings in the output.Docs: conan-io/docs#3215
Close #13517