You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: