Analyzers prototyping #9627
Description
Context
Goals
Functional prototype with sample analyzers
Subtasks:
- Analyzers prototyping - Configuration module #9628 - handles loading user settings from
.editorconfigin a structured form. Optionally allows passing through unstructured custom key-value configurations for the rules - Analyzers prototyping - Instrumentation module #9629 - Handles opt-in monitoring of overhead added byt the analyzers infra and individual analyzers
- Analyzers prototyping - Loading and acquisition #9633
- Analyzers prototyping - Subscription and data API #9631 - indirection and abstraction layer between the actual data from MSBuild and their consumption in analyzers
- Analyzers prototyping - Infrastructure #9632 - responsible for consuming the configuration and loaded modules running the registrations, pumping underlying data to analyzers and wrapping and routing the results
- Analyzers prototyping - Representative analyzers set #9630 - identification and implementation
- Analyzers prototyping - Opting in/out #9723
- Analyzers prototyping - properly inject bootstrap location into tests #9729
Other work:
- Analyzers prototyping - Bootstrap adjustments #9734
- Analyzers prototyping - Detect and skip restore (evaluation and execution) #9747
- Detect current msbuild file and have it as part of analysis context - when asking for configuration (plus contexts might need to be preserved and switched)
- Detect the root of the build - for analyzers that are checking references outside of the root of the build (https://github.com/orgs/dotnet/projects/373/views/1?pane=issue&itemId=55808682)
- BuildCheck connector for binlog replaying #9760
- Canonicalize paths on Mac so analyzers can compare them (this is the workaround for now) (https://github.com/orgs/dotnet/projects/373/views/1?pane=issue&itemId=55702688)