Introduce a WarningsAsErrors block to Robust.Properties.targets #5421
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
|
wasnt aware you could do this for individual warnings, good idea imo |
|
The duplicate |
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.
One way to have fewer warnings is to turn some warnings into errors.
I have one suggestion to start off:
CS0105which is the duplicateusingwarning. I don't think I care too much about unused usings but duplicate usings should definitely be an error.It helps take some of the load off of maintainers by turning incidental shit that causes warnings into quick failures. It's not a big ask for either us or downstreams to correct either, so I seems like a no brainer.