About clientOptions.workspaceFolder.uri of LanguageClientConfig must be a real physical disk path?

[yswang0927]

Hi, @kaisalmen

I use @codingame/monaco-vscode-api and our monaco-languageclient to implements java editor and java-lsp(eclipse.jdtls).

I didn't use the monaco-languageclient/vscodeApiWrapper api to create the editor, but instead created the full vscode workbench in the original way of @codingame/monaco-vscode-api .

By way of the combination, I successfully connected to the Java - LSP - server (lsp is working properly), but I found the LanguageClientConfig-clientOptions.workspaceFolder.uri must be a real physical disk path, if it is a non-existent path or memory path, the lsp will not take effect.

The clientOptions. workspaceFolder.uri must be a real physical disk path, right?

The initLspClient source:

[kaisalmen]

The clientOptions. workspaceFolder.uri must be a real physical disk path, right?

Hi @yswang0927 short answer: yes. It is one of the reason why we use a Container for eclipse.jdt.ls in our example as we can ensure the workspace exists on the file system.

[yswang0927]

Hi @yswang0927 short answer: yes. It is one of the reason why we use a Container for eclipse.jdt.ls in our example as we can ensure the workspace exists on the file system.

Got it. Thank you!
However, the physical path is not very convenient for web editor.