Skip to content

Conversation

@stephentoub
Copy link
Member

Use Microsoft.CodeAnalysis.Analyzer in our builds, to help validate our analyzers and source generators. A few projects were doing this explicitly; this does it for all.

Note that for Environment.NewLine, there's a debate happening about it in dotnet/roslyn-analyzers#6467. I chose to silence the warnings by making tweaks to the code that don't actually impact what's generated but that make the use of the banned symbol go away.

Use Microsoft.CodeAnalysis.Analyzer in our builds, to help validate our analyzers and source generators. A few projects were doing this explicitly; this does it for all.
@ghost
Copy link

ghost commented Sep 7, 2023

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

Issue Details

Use Microsoft.CodeAnalysis.Analyzer in our builds, to help validate our analyzers and source generators. A few projects were doing this explicitly; this does it for all.

Note that for Environment.NewLine, there's a debate happening about it in dotnet/roslyn-analyzers#6467. I chose to silence the warnings by making tweaks to the code that don't actually impact what's generated but that make the use of the banned symbol go away.

Author: stephentoub
Assignees: stephentoub
Labels:

area-Meta

Milestone: -

Copy link
Member

@sbomer sbomer left a comment

Choose a reason for hiding this comment

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

ILLink changes LGTM, thanks!

@stephentoub stephentoub merged commit 7d399f6 into dotnet:main Sep 8, 2023
@stephentoub stephentoub deleted the analyzeranalyzers branch September 8, 2023 14:08
@ghost ghost locked as resolved and limited conversation to collaborators Oct 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants