-
-
Notifications
You must be signed in to change notification settings - Fork 209
All types are stale while origin is not explicitly saved #636
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
Your guess is right, it's a separate TS language server instance running. It's because it's not possible to my knowledge to add additional behavior on top of the existing TS server. There are TS plugins but those only run in the IDE, not when executing ts from the command line , so something like If you know ways to improve it, I'm eager to hear your suggestions. Related: #580 |
Maybe we can solve this in a way specific to the vscode extension by listening to other documentchange-events in the client and forward ts/js changes (denounced, 1 second) through a specific event to the language server. Diagnostics could be triggered afterwards, too. |
sveltejs#636 Listen to document text changes and manually update TS/JS files in the language server through a dedicated notification message
#636 Listen to document text changes and manually update TS/JS files in the language server through a dedicated notification message
A type coming from any other file will be stale until that other file is saved


My main concern is about the place where the extension gets the stale types from, I hope that those types being stale does not mean that the extension is running a whole duplicate typescript language server concurrent to the one vscode runs for standard
.ts
filesThat would certainly explain why svelte types are only available within
.svelte
files... Is it a misconfiguration on my part ?The text was updated successfully, but these errors were encountered: