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

Add way for extensions to signal that diagnostics are actively being computed but have not been returned yet #54273

Closed
mjbvz opened this issue Jul 13, 2018 · 1 comment
Assignees
Labels
api feature-request Request for new features or functionality languages-diagnostics Source problems reporting *out-of-scope Posted issue is not in scope of VS Code under-discussion Issue is under discussion for relevance, priority, approach
Milestone

Comments

@mjbvz
Copy link
Collaborator

mjbvz commented Jul 13, 2018

Problem
Sometimes it may take a few seconds to return diagnostics in a file (especially when you first open a workspace). We would like a way to signal to users that diagnostics are actively being computed but are not being shown yet. This piece of information could also be used at other points in the VS Code UI (such as preventing f5 for example)

Possible solutions
We discussed a few potential ideas around this at the FB meeting:

  • Add API so that an extension / language server can signal that diagnostics are actively being computed for a given file
  • Encourage extensions to return a fake diagnostic that says "diagnostics are being computed"
  • Add a pull model for diagnostics so that we can determine

(This came out of the FB meeting)

@mjbvz mjbvz changed the title Add way for extensions to signal the diagnostics are actively being computed but have not been returned yet Add way for extensions to signal that diagnostics are actively being computed but have not been returned yet Jul 13, 2018
@jrieken jrieken added feature-request Request for new features or functionality under-discussion Issue is under discussion for relevance, priority, approach languages-diagnostics Source problems reporting labels Jul 16, 2018
@jrieken jrieken added the api label Oct 8, 2019
@jrieken jrieken added this to the Backlog milestone Nov 8, 2019
@jrieken jrieken added the *out-of-scope Posted issue is not in scope of VS Code label Nov 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api feature-request Request for new features or functionality languages-diagnostics Source problems reporting *out-of-scope Posted issue is not in scope of VS Code under-discussion Issue is under discussion for relevance, priority, approach
Projects
None yet
Development

No branches or pull requests

4 participants
@jrieken @dbaeumer @mjbvz and others