microsoft / microsoft/vscode-wasm
LSP URI converter generate invalid paths when workspace URI has a trailing `/`
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 456
- Forks
- 40
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 4
Description
When running an extension using the vscode-test-web tool, the default workspace is mounted under vscode-test-web://mount/. This trailing / causes issues with the LSP URI converter.
For example:
- The code-to-protocol maps
vscode-test-web://mount/a/file.txttofile:///workspacea/file.txt(rather thanfile:///workspace/a/file.txt). - The protocol-to-code converter maps
file:///workspace/a/file.txttovscode-test-web://mount//a/file.txt(this isn't as serious, though does mean the URL is no longer normalised).
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 by reproducing the LSP URI converter cases described for the vscode-test-web workspace URI vscode-test-web://mount/. Trace both code-to-protocol and protocol-to-code conversions, then verify that workspace paths retain the separator and URLs remain normalized for the examples in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100