-
Notifications
You must be signed in to change notification settings - Fork 30k
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
workspace/didChangeWatchedFiles
is not always sent for deleted folders
#65077
Comments
@LaurentTreguier can you provide me with a GitHub repository with two branches that make it easy to reproduce this. I tested this locally with Windows 10 and I works for me. |
It looks like this might not be the correct repository for this issue, I've tried a few more things and the problem seems to lie with I'm experiencing this with the language server I'm developing.
When doing this, I see some messages appearing in the debug console about files being created and changed, but no mention of files in the |
@LaurentTreguier thanks. I will move the issue to the vscode repository. |
@LaurentTreguier please check if this could be #60813 |
Looks like. We do send a delete event in the example but only for |
/duplicate #60813 |
Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines. Happy Coding! |
Sometimes, if I delete a folder, I won't get any
workspace/didChangeWatchedFiles
notification. I saw #141, which seemed somewhat similar, but here I'm somehow not even getting a notification about the folder itself being deleted.I looked directly at the JSON-RPC requests and notifications that my server is receiving, in case I did something wrong, and saw no notification about anything being deleted in a session where I removed a folder.
I noticed this when switching branches in a project, where one branch has a folder that the other doesn't have.
If this is of any use:
vscode-languageclient
: 5.1.1I'll see if I can reproduce this on Windows to know if this is platform-specific.
EDIT: it seems to be doing the same on Windows 10 x64.
The text was updated successfully, but these errors were encountered: