microsoft / microsoft/vscode-languageserver-node
Option to control `workspaceFolders` in `InitializeParams`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 404
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 14
Description
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.
Are there other paths that I can use to filter out non-file type folders when building the initialize request message?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with client/src/common/workspaceFolder.ts at WorkspaceFolderFeature.fillInitalizeParam and inspect how WorkspaceFolderMiddleware is applied during initialization. Trace the construction of initializeParams and determine whether an option or hook can control workspaceFolders; done means non-file folders can be excluded or otherwise controlled in the initialize request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100