Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Do not upgrade warnings to errors in VS #39845
Open
+1
−1
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
Now that we have enabled a bunch of code analysis, we've discovered it adds friction to the dev process. This change aims to reduce the friction by preventing warnings to be upgraded to errors in VS. This way you can continue developing, while possible issues are still surfaced. E.g. from a recent error:
wtgodbe
approved these changes
Jan 28, 2022
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.
Now that we have enabled a bunch of code analysis, we've discovered it adds friction to the dev process. This change aims to reduce the friction by preventing warnings to be upgraded to errors in VS. This way you can continue developing, while possible issues are still surfaced. E.g. from a recent error:
The text was updated successfully, but these errors were encountered: