chore: Replace StyleCop.Analyzer library to unstable version #2796
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR intended to replace
StyleCop.Analyzerslibary to StyleCop.Analyzers.Unstable version.Background
StyleCop.Analyzerspackage stable version (1.1.118) is released at 2019/04/29.It don't support syntax that are added by C# 8.0 or later.
And it cause build error when applying code formatter with Visual Studio (e.g. when using target-typed new statement)
StyleCop.Analyzers.Unstable is officially released package to handle this issue, and it seems widely used compared to
-betaprefixed version. (It's compared by download count)What's changed in this PR
StyleCop.Analyzers.Unstable. And addIncludeAssetssetting that shown on NuGet package page. (01b3f04)