Document the impact SdkAnalysisLevel has #47456
Draft
+11
−0
Conversation
This file contains hidden or 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
nkolev92
changed the title
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.
Summary
Document the impact SDKAnalysisLevel has.
This is important because often customers may set this value to unblock themselves due to a particular warning, but they're potentially unknowingly disabling a lot more.
I am starting this table to serve as a guide for customers setting SDKAnalysisLevel
I'd love to be able to reference this from the NuGet docs wherever we recommend that people can set SDKAnalysisLevel to go back to the old behavior.
Fixes NuGet/Home#14369
Internal previews