-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
chore: separate tslint config files for build and vscode #969
Conversation
37487a2
to
951616f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IIUC, this is an undo of the previous commit. But we will end up without a check for unused import again.
Is it possible to update the package.json
"tslint" script to pass it tslint.build.json
as the config? (And that might remove the warning for tslint plugin for VSCode).
Not really. Please note that CLI build uses |
By CLI do you mean |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see. So it doesn't pick it up the the top level tslint.json
which extends tslint.common.json
? That seems strange but ok. As long as it catches unused imports :)
Maybe wait till @bajtos / @kjdelisle have a chance to review this as well before merging.
Yes, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great, thank you @raymondfeng for fixing the problems introduced by your previous PR 👏
I have checked out your feature branch and verified that:
- vscode-tslint does not report any warnings
- unused variables are reported by
npm run tslint
I think you have a bug in the tslint.build.json
template (see my comment below).
Other than that, this patch LGTM 👍
"no-floating-promises": true, | ||
"no-void-expression": [true, "ignore-arrow-function-shorthand"] | ||
} | ||
"extends": ["./node_modules/@loopback/build/config/tsconfig.build.json"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you have a typo here - are you sure that tslint.build.json
should be extending tsconfig.build.json
? I think you meant to extend tslint.build.json
instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch. Fixed.
This is a follow-up to #964. Two config files are in place now: - tslint.build.json for CLI build scripts - tslint.json for vscode
951616f
to
b622910
Compare
This is a follow-up to #964.
Two config files are in place now:
Checklist
npm test
passes on your machinepackages/cli
were updatedpackages/example-*
were updated