[release/10.0] Set IDE0031 to suggestion in eng/CodeAnalysis.src.globalconfig #119755
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.
Alternative solution for the backport of #119722
Instead of backporting fixing the IDE0031 which is a quite large change we just turn the severity into
suggestion.Customer Impact
There's a Roslyn bug where the
suggestionseverity fordotnet_style_null_propagationin .editorconfig incorrectly overrides the IDE0031warningseverity set in eng/CodeAnalysis.src.globalconfig on some machines only (root cause is currently being investigated in dotnet/roslyn#80301).This causes build breaks on machines where this doesn't happen and the IDE0031 warning severity is active.
Regression
Testing
The CI build verifies this works.
Risk
Low. This just turns an analyzer code style finding from warning to suggestion.