Provide "recommended" and "latest" configurations
See original GitHub issueEnhancement Request
tslint
supports configuration extensions via "extends"
json option. This is a very convenient way of reusing configurations and keeping up-to-date with latest linter advancements.
Given the roadmap for codelyzer, it’s obvious that there will be linting rules added in the future. To allow developers take advantage of these, it would be convenient if codelyzer
provided a set of preconfigured settings. There’s already a “Recommended Configuration” section in the readme, so why not extract that to a “.json” file?
Given that "extends"
option also supports “the name of an NPM module which has a “main” file that exports a config object”, the package.json
file could also be modified to export the, say, “recommended” configuration:
"main": "presets/ng2-recommended.json"
Or, even better, “recommended” and “latest” configurations could be their separate npm packages.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:3
- Comments:5 (1 by maintainers)
@mgechev any updates about this suggestion?
@mgechev Have you though about this? I think it will be useful to include the recommended rules to be active, and a great way to have the
Codelyzer Verify
.