Option to control `workspaceFolders` in `InitializeParams`

[hyangah]

Sorry for opening an issue to ask questions.

We (Go extension) are using this client library to interact with the go language server. Currently the server assumes all workspace folders have file://-scheme. In vscode, however, that's not always true - some extensions register virtual file systems and their folders can be added as workspace folders. I hoped that we could use the WorkspaceFolderMiddleware. But, I suspect this is not used when populating the workspaceFolders property of the initializeParams.

The WorkspaceFolderFeature's fillInitalizeParam calls vscode.workspace.workspaceFolders directly.

vscode-languageserver-node/client/src/common/workspaceFolder.ts

Line 56 in 31fe8fe

const folders = workspace.workspaceFolders;

Are there other paths that I can use to filter out non-file type folders when building the initialize request message?

[dbaeumer]

The only way I can currently think of is subclassing the client and overriding fillInitializeParams and patching the workspace folders there. This being said, subclassing is generally not recommended and this might break in future versions.

The correct way would be to provide a hook via the client options.