Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / dotnet/roslyn-analyzers-contrib issues and pull requests

#19 - Document testing pattern for diagnostics which include code fixes

Issue - State: open - Opened by sharwell about 9 years ago - 2 comments

#18 - Make sure iteration counts are tested for Fix All providers

Issue - State: open - Opened by sharwell about 9 years ago

#16 - Make it easy to test analyzer and code fixes on real open source projects

Issue - State: open - Opened by giggio about 9 years ago - 3 comments

#15 - Guidelines on how to test analyzer performance

Issue - State: open - Opened by giggio about 9 years ago - 3 comments

#14 - Fix #10: First cut at "Inventory of Epics"

Pull Request - State: closed - Opened by ghost over 9 years ago - 6 comments

#13 - roslyn-analyzer-seed template

Issue - State: open - Opened by ghost over 9 years ago - 3 comments
Labels: Feature request, Area-Tooling

#12 - Move the Roslyn SDK source to this repo

Issue - State: closed - Opened by srivatsn over 9 years ago - 1 comment

#11 - Stub generation tool

Issue - State: open - Opened by ghost over 9 years ago
Labels: Feature request, Area-Tooling

#10 - Create inventory of "epics"

Issue - State: closed - Opened by ghost over 9 years ago - 4 comments

#9 - Tool to create issues for new analyzers

Issue - State: closed - Opened by ghost over 9 years ago - 1 comment
Labels: Feature request, Area-Tooling

#7 - What updates to VS do we require to advance the analyzer eco-system?

Issue - State: open - Opened by michaelcfanning over 9 years ago - 2 comments

#4 - What supporting test infrastructure can we share?

Issue - State: open - Opened by michaelcfanning over 9 years ago

#3 - What additions/modifications of Roslyn metadata would be useful?

Issue - State: open - Opened by michaelcfanning over 9 years ago - 1 comment

#2 - Roslyn SDK/guidelines

Issue - State: open - Opened by michaelcfanning over 9 years ago