Skip to content
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

Fix warnings and apply suggestions. #767

Merged
merged 2 commits into from
Aug 20, 2020

Conversation

JoeRobich
Copy link
Member

I locally updated the TFM to net5.0. I fixed the reported nullability warnings and applied the analyzer suggestions that were offered.

@JoeRobich JoeRobich requested a review from jmarolf August 20, 2020 04:09
@@ -11,7 +11,7 @@
"/property:GenerateFullPaths=true",
"/consoleloggerparameters:NoSummary"
],
"problemMatcher": "$msCompile"
"problemMatcher": []
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do you know what this change is about?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I should have talk about this one. So OmniSharp will report diagnostics in the Problems tab. Running a build using a problems matcher will report build warnings and errors in the Problemss tab. This will duplicate warning and errors in the Problems tab amd the build reported problems won't go away until a new build is run. So, removing the problemMatcher will keep duplicate, zombie issues from entering the Problems tab.

@JoeRobich JoeRobich merged commit d73e027 into dotnet:master Aug 20, 2020
@JoeRobich JoeRobich deleted the fix-nullability-warnings branch March 5, 2021 21:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants