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
{{ message }}
This repository has been archived by the owner on Dec 25, 2019. It is now read-only.
Currently tslint.json is hard coded.
But tslint and tslint-microsoft-contrib provide different presets (all/recommended/latest,...) Some of them are offered as .js files when installing vie npm (and .ts files in the sources?)
It is also supported to use tslint.yaml or actually any other name.
As long as we are writing to fixed report file names, they should be derived from the config we analyzed, so they will stock close to the analyzed config in the file system.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently
tslint.json
is hard coded.But tslint and tslint-microsoft-contrib provide different presets (all/recommended/latest,...) Some of them are offered as .js files when installing vie npm (and .ts files in the sources?)
It is also supported to use tslint.yaml or actually any other name.
As long as we are writing to fixed report file names, they should be derived from the config we analyzed, so they will stock close to the analyzed config in the file system.
The text was updated successfully, but these errors were encountered: