Skip to content
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

Run Roslyn Analyzers and CodeFixes #416

Closed
JoeRobich opened this issue Nov 6, 2019 · 3 comments
Closed

Run Roslyn Analyzers and CodeFixes #416

JoeRobich opened this issue Nov 6, 2019 · 3 comments
Assignees
Labels
Feature Request This issue is requesting an enhancement or new feature

Comments

@JoeRobich
Copy link
Member

JoeRobich commented Nov 6, 2019

Configuration for diagnostic severity can now be expressed in .editorconfig files. dotnet format should be able to run diagnostics and apply fixes for those of a specified severity.

As a first step dotnet format could support the known set of CodeStyle diagnostics and fixes in Roslyn.
As a further enhancement it could run Analyzers installed via NuGet.

@OneCyrus
Copy link

any update on this? i think that's the main feature everyone is waiting for.

@JoeRobich
Copy link
Member Author

To support analyzers and fixes the following work items need to be completed:

  1. Move to Roslyn .editorconfig support (Move to Roslyn's editorconfig support #590) which is currently blocked by a performance regression.
  2. Implement Analyzer & CodeFix discovery that doesn't require Roslyn IVTs
  3. Move the analysis and codefix support over from the feature/analyzers branch

@jmarolf
Copy link
Contributor

jmarolf commented Jul 2, 2020

closed with #713

@jmarolf jmarolf closed this as completed Jul 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request This issue is requesting an enhancement or new feature
Projects
None yet
Development

No branches or pull requests

3 participants