-
-
Notifications
You must be signed in to change notification settings - Fork 353
Current status of didChangeWorkspaceFolders
#1810
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
Comments
It should be supported since 3.5.1, but I forgot to change the wiki. |
I have tested it in VSCode Windows and it works normally. |
This my server log for backlog. |
Yes, I know that the VSCode extension restarts the server. That's why the VSCode extension works just fine for me.
Right, I think this is non-standard behaviour. Other LSPs doesn't require the user to do this. Can we have the same behaviour with lua-language-server? |
Could you provide a example RPC log? I will try to build a test case. |
Of lua-language-server? or Pyright? |
Of lua-language-server, then I can simulate the client to send these protocols to the server in the test, likes this: https://github.com/sumneko/lua-language-server/blob/master/test/tclient/tests/change-workspace-folder.lua |
Btw, does that test actually work? I'm not completely sure of how it works, but I don't see any restarts in-between the workspace changes. |
This feature is designed without restart. |
Here's my log, with |
Thank you for the fix! |
This LSP implements a handler for
didChangeWorkspaceFolders
, but it does not really work correctly (especially on Windows).The documentation does mention that workspaces cannot be dynamically modified, so I'm not sure why is there a handler for
didChangeWorkspaceFolders
.It also seems that the official VSCode extension restarts the server instead of sending
didChangeWorkspaceFolders
when a new folder is added, which further questions what the handler is there for.This is a fairly non-standard behavior, as servers are expected to handle
didChangeWorkspaceFolders
properly if workspace folders are supported. Surprises like this adds hurdles when developing clients for non-VSCode editors.So, are there any plans for dynamic workspaces in the near feature, or are clients expected to restart the server for the foreseeable future?
The text was updated successfully, but these errors were encountered: