search

dotnet / roslyn-analyzers-contrib

Replaced by dotnet/roslyn-analyzers.
https://github.com/dotnet/roslyn-analyzers
Apache License 2.0
16 stars 8 forks source link

What updates to Roslyn itself do we require to advance the analyzer eco-system? #5

Open michaelcfanning opened 8 years ago

michaelcfanning commented 8 years ago
  1. Identify internal APIs that need to be public
  2. Identify cross-analyzer relevant utility code to push into the platform
  3. Identify a format to express analyzer properties and an improved mechanism for piping these to analyzers
  4. Related to above, provide a mechanism for rolling up configuration at the project/sln/enlistment level
  5. Related, reconceive rulesets using improved configuration story, as above
  6. Provide high-speed per-document, per-project, etc. fix all providers
  7. Consider whether requirement to publish refactorings as hidden diagnostics + fixers is appropriate/tenable
  8. Pipe exceptions back to well-known plug-in authors
  9. Pipe other use telemetry back to plug-in authors
  10. Provide useful/not-useful up and down votes for diagnostic instances, pass back to plug-in authors

Likely individual items from this list (and those contributed by others) will warrant their own discussion threads.