ionide / ionide/FSharp.Analyzers.SDK
One analyzer with multiple messages/codes, or multiple analyzers?
- Dominant language
- F#
- Stars
- 85
- Forks
- 28
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 20
Description
I'm experimenting with an F# linter, [Flinter](https://github.com/cmeeren/Flinter). Like most linters, it will have quite a lot of rules.
Should I implement each rule as a separate analyzer, or should I implement one analyzer for the entire linter and then delegate work internally? I'm currently leaning toward the former, but that decision is not based on a lot of information.
This may need to be seen in light of other issues like #8, and may not make sense to consider at the moment. Still, I wanted to post the question here, at least just for future consideration and to make it easier to "keep in the back of the head" while working on other features like #8.
Any input is welcome.
Contributor guide
Assessment
This issue has not been assessed yet.