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

Use builder logic (now used for compile on save) to retrieve diagnostics for tsserver #11229

Open
mhegazy opened this issue Sep 28, 2016 · 5 comments
Labels
Experience Enhancement Noncontroversial enhancements Suggestion An idea for TypeScript VS Code Tracked There is a VS Code equivalent to this issue
Milestone

Comments

@mhegazy
Copy link
Contributor

mhegazy commented Sep 28, 2016

Now that we have the builder logic that optimizes what files to read. we should use this for getDiagnostics.

@PFight
Copy link

PFight commented Jul 4, 2018

Can we hope to see this sometime?
Comple-on-save is awesome feature for large-scale projects, it is very sad, that no one editor can support it well (and VSCode not support at all) without this.

@RyanCavanaugh RyanCavanaugh added the Experience Enhancement Noncontroversial enhancements label Aug 15, 2018
@weswigham weswigham removed the Suggestion An idea for TypeScript label Nov 6, 2018
@RyanCavanaugh RyanCavanaugh added the Suggestion An idea for TypeScript label Mar 7, 2019
@TomasHubelbauer
Copy link

TomasHubelbauer commented Apr 24, 2019

Would be really cool to get at least a rough estimate (this year?) as this is a blocker for microsoft/vscode#13953 which is very painful.

@andrecasal
Copy link

Would love a status update on the progress for this feature from the TS team. Like @TomasHubelbauer said, this is a missing key feature in VS Code (microsoft/vscode#13953) and a deal breaker for large projects.

@olafur-palsson
Copy link

olafur-palsson commented Aug 13, 2021

Any status updates so far? It's been a couple of years now. This is now a much needed feature for the typescript.tsserver.experimental.enableProjectDiagnostics feature in vscode which is currently using the geterrForProject route.

@v-karbovnichy
Copy link

The blocked issue in VSCode microsoft/vscode#13953 have already 1380 thumbs-ups, and both are not really moving for 8+ years.

Well, nothing really to add here: "this is a missing key feature in VS Code ... and a deal breaker for large projects."

Wake up, please.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Experience Enhancement Noncontroversial enhancements Suggestion An idea for TypeScript VS Code Tracked There is a VS Code equivalent to this issue
Projects
None yet
Development

No branches or pull requests

10 participants