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

Categorization of rules with configuration? #708

Open
Thorium opened this issue Apr 4, 2024 · 0 comments
Open

Categorization of rules with configuration? #708

Thorium opened this issue Apr 4, 2024 · 0 comments

Comments

@Thorium
Copy link
Member

Thorium commented Apr 4, 2024

The current config is like 70+ rules.
It would be nice to have them in categories, for example:
Execution speed, Memory usage, Naming, Coding convention

For example, a nested JSON configuration file instead of current list.
Or maybe like FxCop used to have, provide multiple pre-defined configuration files:
fsharplint-recommended.json, fsharplint-performance.json, fsharplint-maintainability.json, fsharplint-all.json, ...

Because, for new project you'd want a different config than for existing project, and sometimes you look to improve a specific aspect of the source code. That could make easier adaptation of this tool for existing libraries.

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