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 Mar 25, 2021. It is now read-only.
$ node_modules/.bin/tslint --type-check src/test.ts
Warning: The 'completed-docs' rule requires type checking
Expected behavior
Shouldn't I get a message about documentation missing? Sadly https://palantir.github.io/tslint/rules/completed-docs/ just displays a white page for me. Maybe I'm just using or imagining it wrong but ideally, I'd like to enforce everything being documented.
The text was updated successfully, but these errors were encountered:
For --type-check to work you also need to pass --project ./path/to/tsconfig.json as stated in the CLI documentation. Also the file you want to lint needs to be part of you project (included in tsconfig.json)
But maybe that should also be printed as error or warning ...
Okay, that solved it. In the actual script I am running I just passed -p tsconfig.json, but tslint needs --project. I assumed I could pass it as -p like with tsc.
[bugfix] exit with 0 on type check errors when `--force` is specified
Fixes: #2087
[bugfix] `--test` now correctly strips single quotes from patterns on windows
[enhancement] `--test` can handle multiple paths at once
[enhancement] added `-p` as shorthand for `--project` to be consistent with `tsc`
Kind of fixes: #2291
[enhancement] print error when `--type-check` is used without `--project`
[enhancement] don't print stack trace on type check error
Bug Report
4.5.1
2.0.2
TypeScript code being linted
with
tslint.json
configuration:Actual behavior
Expected behavior
Shouldn't I get a message about documentation missing? Sadly https://palantir.github.io/tslint/rules/completed-docs/ just displays a white page for me. Maybe I'm just using or imagining it wrong but ideally, I'd like to enforce everything being documented.
The text was updated successfully, but these errors were encountered: