This repository has been archived by the owner on Jul 15, 2023. It is now read-only.
Use tsconfig.json to determine which typescript files to lint #2524
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
|
I think the ci failures are the same as on master. |
ramya-rao-a
approved these changes
Jun 5, 2019
There was a problem hiding this comment.
Thanks for the PR @stuartgrigg and apologies for the late response.
Looks like this is your first PR contribution to this project, Thanks & Welcome!
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed that the
npm run lintcommand was not covering all the typescript files in the repo and was therefore missing some linting errors. I have changed this command and thenpm run fix-lintcommand so that they use the tsconfig.json file to determine which files will be linted. I have also used the fix-lint command to fix the errors which my change had uncovered.