-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Update code style layer to Microsoft.CodeAnalysis 3.3.1 #41096
Conversation
a8c8857
to
35a3a00
Compare
35a3a00
to
22b2526
Compare
a34c071
to
00df672
Compare
|
||
namespace Microsoft.CodeAnalysis | ||
{ | ||
internal abstract class OptionSet | ||
internal sealed class CompilerAnalyzerConfigOptions : AnalyzerConfigOptions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this type being used anywhere now? Seems weird as its TryGetValue always returns false.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great to see all the deleted code! Bit unfortunate we now need the #if CODE_STYLE
in all the formatting related files.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Attempting to load Microsoft.VisualStudio.CodingConventions via the diagnostic analyzer service causes conflicts with Visual Studio extensions that depend on the same assembly. See pharring/EditorGuidelines#21 for example. This change updates the code style layer to use the new .editorconfig support from the compiler exclusively, and removes the dependency on Microsoft.VisualStudio.CodingConventions.
Following this change, the NuGet-installed FormattingAnalyzer requires Roslyn 16.3 or newer.