Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign up'standard' on TypeScript generating incorrectly claiming symbols never used #948
Comments
This comment has been minimized.
This comment has been minimized.
samvv
commented
Jul 7, 2017
|
With the new code on |
This comment has been minimized.
This comment has been minimized.
|
@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. |
This comment has been minimized.
This comment has been minimized.
samvv
commented
Jul 7, 2017
|
Oh whoops, I see now, missed that. |
This comment has been minimized.
This comment has been minimized.
|
This can be closed. Known typescript-eslint-parser issue: |
LinusU
closed this
Oct 2, 2017
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.
BurtHarris commentedJul 7, 2017
•
edited
I've tried setting up
standardto process TypeScript files usingtypescript-eslint-parserandeslint-plugin-typescriptas 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.tsgives me these these messages: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