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

Regularly run analysis in the background #2

Open
marinaglancy opened this issue Oct 26, 2023 · 1 comment
Open

Regularly run analysis in the background #2

marinaglancy opened this issue Oct 26, 2023 · 1 comment

Comments

@marinaglancy
Copy link
Owner

This is a feature mentioned in the vscode issue microsoft/vscode#13953 (comment)

I just wanted to create an issue in my repository so we can discuss it here.

For starter I want to say that I do not currently know how to do it without disturbing the normal work process. In order to trigger the diagnostics analysis there should be an event notifying other extensions that they need to analyse the file. They usually listen to "file opened" or "file edited" events . And the way VSCode works is that it unloads the problems if the file was opened a long time ago but was not interacted with.

"Bulk problem diagnostics" has to bring such files to the foreground and it will shift a focus from the currently edited file, which makes it impossible to run in the background

@ADTC
Copy link

ADTC commented Oct 26, 2023

From what I noticed, it switches to files that are already open (but otherwise don't visually open them). So a periodic run in the current workflow would definitely be a disturbance to the user.

I think this isn't very urgent, and if there is no easy solution, it's alright to not have any.

You can consider adding an optional status bar button to invoke the analysis manually, and perhaps to control some options like severity level quickly from its context menu.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants