-
Notifications
You must be signed in to change notification settings - Fork 202
[bug] erroneous type errors #1487
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
Comments
The |
Alright, now looks like I've reached an unrecoverable state. No matter how many times I restart Atom, I am no longer seeing any time information or errors at all, in the entire project. I haven't touched any configs, I've been editing only a single source file (the one in the screenshot above). |
Don't know if it's related, but I'm seeing an errors like the following occurring in the console: continued: continued:
|
My typescript experience is totally borked. Restarted Atom completely (quit all windows, kill Atom) and still the same issues: erroneous errors, etc. |
Looks like type PointGroups = {
[key in keyof Pick<Layers, 'base1' | 'base1color'>]: THREE.Group
} was the source of all problems. When I changed it to type PointGroups = {
[key in keyof Pick<typeof Layers, 'base1' | 'base1color'>]: THREE.Group
} with the insertion of the With out the The tsc compiler would tell me that it could not find the name But nonetheless, I don't think atom-typescript intends to become totally unusable when this case happens. |
I feel that |
Looks to be an edge case that atom-typescript (or the ts server?) isn't handling well when I'm incorrectly passing the |
Thanks for the report. Long story short you've apparently run into microsoft/TypeScript#25456, which is obviously upstream bug. Perhaps tsserver errors should probably be reported more visibly to avoid unnecessary confusion? I'll see what I can do with that. |
Here's a screenshot, notice that the tooltip shows a type error that has nothing to do with the line where it is showing the error:
I don't know how to reproduce it. It just happens sometimes. The only way to recover is
control
+option
+command
+l
to restart.The text was updated successfully, but these errors were encountered: