Add possibility to silence some warnings #3035
Merged
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
cphyc
added
enhancement
|
Seems good to me! |
matthewturk
approved these changes
Jan 25, 2021
Co-authored-by: Clément Robert <cr52@protonmail.com>
neutrinoceros
approved these changes
Jan 25, 2021
This was referenced Jan 26, 2021
Closed
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.
PR Summary
As devs, we may want to silence some warnings when developing. For example, we may want to ignore the warning that both
~/.config/yt/ytrcand~/.config/yt/yt.tomlexist when working on both yt 3 and yt 4.This PR adds supports for adding a list of warnings to simply ignore for devs convenience. I did not write any doc for this, as it is intended for devs only (otherwise users may simply ignore all warnings).
To use it, find the warning that is getting on your nerve, and save it in your config using