Skip to content
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

Using custom project and config options together #3

Open
boenrobot opened this issue Jan 9, 2019 · 0 comments
Open

Using custom project and config options together #3

boenrobot opened this issue Jan 9, 2019 · 0 comments

Comments

@boenrobot
Copy link

I am trying to use this plugin to check for TSLint checks that require type information.

The docs would seem to suggest that specifying
project: '.'

should work, but I get an error saying "Failed to find TSLint configuration".

Explicitly specifying the path to the tslint.json file (not the folder) is more akin to the -c option than the -p option though, in that I get an error saying certain hints require type information. And specifying the path to the tsconfig.json file (not the folder) says "No valid rules have been specified for TypeScript files" and effectively skips tslint.

Is there a way I can actually use both options?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant