Support editorconfig for defining diagnostic severity levels
- Dominant language
- C#
- Stars
- 5.5k
- Forks
- 1.5k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 141
Description
### Summary
Today we support editorconfig for buildcheck diagnostic configurations - but across the stack users are able to use editorconfig to configure Roslyn analyzer and source generator behaviors as well. In practice, this feels a lot like managing the behavior of MSBuild diagnostics, but users hit a wall when they try to do so. We should feed in editorconfig configuration to the decision-making around how to log a diagnostic.
### Background and Motivation
* Unifying the control plan for diagnostics of all kinds
* Enabling control of this outside of the 'MSBuild bubble'
* Better UX
### Proposed Feature
We should feed in editorconfig configuration to the decision-making around how to log a diagnostic.
### Alternative Designs
_No response_
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.