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

'standard' on TypeScript generating incorrectly claiming symbols never used #948

Closed
BurtHarris opened this issue Jul 7, 2017 · 4 comments

Comments

@BurtHarris
Copy link

commented Jul 7, 2017

I've tried setting up standard to process TypeScript files using typescript-eslint-parser and eslint-plugin-typescript as documented in the README. It's given me some nonsensical errors claiming some of my imports are never being used, when it's plain they are. For example, standard src/documenter.ts gives me these these messages:

standard: Use JavaScript Standard Style (https://standardjs.com)
  C:\code\tsdoc\src\documenter.ts:2:13: 'ts' is defined but never used.
  C:\code\tsdoc\src\documenter.ts:3:27: 'interfaces' is defined but never used.
  C:\code\tsdoc\src\documenter.ts:4:10: 'DocumenterOptions' is defined but never used.
  C:\code\tsdoc\src\documenter.ts:4:29: 'RunOptions' is defined but never used.

When in fact all four of these symbols are in use. See source code here

standard version: 10.0.2
tsc version: 2.3.4

@samvv

This comment has been minimized.

Copy link

commented Jul 7, 2017

With the new code on master, not all of them are in use, but e.g. RunOptions still is, and has always been.

@BurtHarris

This comment has been minimized.

Copy link
Author

commented Jul 7, 2017

@samvv I just used this as an example. The link I provided was to a particular commit, so updates to master on our example project won't (don't need to) be reflected in this issue / bug report.

@samvv

This comment has been minimized.

Copy link

commented Jul 7, 2017

Oh whoops, I see now, missed that.

@mightyiam

This comment has been minimized.

Copy link
Contributor

commented Oct 2, 2017

This can be closed. Known typescript-eslint-parser issue:
eslint/typescript-eslint-parser#77

@LinusU LinusU closed this Oct 2, 2017

@lock lock bot locked as resolved and limited conversation to collaborators May 10, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
4 participants
You can’t perform that action at this time.