-
Notifications
You must be signed in to change notification settings - Fork 93
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
When closing a file, "Problems" should be removed #348
Comments
(This get even worse when you delete a file. You will never get rid of this file's "Problems" until you reload VS Code. |
Currently, the diagnostics is only removed when an external file (outside the workspace root) is closed. The languageserver will load all R files in |
Yes, for the reasons outlined above: it is how most other extensions operate, and once you delete a file, you are stuck with its "Problems" forever otherwise.
I am not working on packages, so I can give useful comments only on the non-packages situation. Having said that: I can see how one should have a more holistic view of one's code in this situation: for example, because packages are often shared publicly or even published in repos which have stricter linting requirements than the average coder's collection of scripts. So I would consider this reasonable. But again, my exposure to this situation is pretty much null. |
OK, then #349 should work for you. For non-package workspace, when you close a file, it will remove its diagnostics. When you delete the file, the text editor is not necessarily closed. When you close its editor, then its diagnostics will be removed too. Does this sound reasonable to you? |
Good point.
Yes, it does. |
You could install the latest development version and see if it works for you. |
I constantly see linting messages from files which I have already closed. Since there is no way to delete them, I feel it would be sensible to remove them when the file is closed.
See also REditorSupport/vscode-R#376 (comment), #292, microsoft/vscode-python#12630, microsoft/vscode#101885, microsoft/vscode#100646
The text was updated successfully, but these errors were encountered: