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

Invest in library-focused Roslyn analyzers #43979

Closed
carlossanlop opened this issue Oct 28, 2020 · 4 comments
Closed

Invest in library-focused Roslyn analyzers #43979

carlossanlop opened this issue Oct 28, 2020 · 4 comments
Assignees
Labels
area-Meta code-analyzer Marks an issue that suggests a Roslyn analyzer code-fixer Marks an issue that suggests a Roslyn code fixer

Comments

@carlossanlop
Copy link
Member

carlossanlop commented Oct 28, 2020

We would like to propose adding the Roslyn Analyzers project as part of the 6.0 objectives to improve .NET.

@buyaa-n and I would like to suggest including this user story in the "Meeting Developer Expectations" Theme, and the "Make sure .NET libraries are continuously improved" Epic from https://dotnetepics.azurewebsites.net/ cc @terrajobst

We have 36 API proposals in the Roslyn Analyzers project that we are going to be driving for review: https://github.com/dotnet/runtime/projects/46

We also have 27 open issues (bugs, enhancements) in the roslyn-analyzers repo, as well as a number of PRs to review to fix or improve the analyzers we own.

cc @mavasani

@carlossanlop carlossanlop added code-analyzer Marks an issue that suggests a Roslyn analyzer code-fixer Marks an issue that suggests a Roslyn code fixer labels Oct 28, 2020
@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added area-Meta untriaged New issue has not been triaged by the area owner labels Oct 28, 2020
@danmoseley
Copy link
Member

@carlossanlop I've added it to https://github.com/dotnet/core/issues/5410 (I simply added a checkbox and link so that it shows up on https://dotnetepics.azurewebsites.net/ ).

You should feel free to add other entries to that as seems appropriate (unless @jeffhandley provides other guidance). We can triage, etc later.

@buyaa-n buyaa-n removed the untriaged New issue has not been triaged by the area owner label Oct 29, 2020
@carlossanlop carlossanlop changed the title User story: Improving our Roslyn Analyzers Invest in library-focused Roslyn analyzers Oct 29, 2020
@danmoseley
Copy link
Member

Moved under #43617 as there's already a user story.

@danmoseley
Copy link
Member

@terrajobst as discussed can you please replace this issue with the specific analyzers we plan to do so they appear in the tree

@terrajobst
Copy link
Member

Done

@ghost ghost locked as resolved and limited conversation to collaborators Dec 25, 2020
@buyaa-n buyaa-n added this to Done in Roslyn Analyzers Mar 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Meta code-analyzer Marks an issue that suggests a Roslyn analyzer code-fixer Marks an issue that suggests a Roslyn code fixer
Projects
No open projects
Development

No branches or pull requests

5 participants