Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

One analyzer with multiple messages/codes, or multiple analyzers? #60

Open
cmeeren opened this issue Jan 2, 2023 · 0 comments
Open

Comments

@cmeeren
Copy link
Contributor

cmeeren commented Jan 2, 2023

I'm experimenting with an F# linter, 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.

@cmeeren cmeeren changed the title One analyzer with multiple messages, or multiple analyzers? One analyzer with multiple messages/codes, or multiple analyzers? Jan 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant