microsoft / microsoft/vscode-wasm
`vscode-file://` protocol address mapping
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 456
- Forks
- 40
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 4
Description
vscode web cannot correctly convert the full path in wasm to a local path using the vscode-file:// protocol, causing the image to fail to render normally.
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 image-rendering failure in vscode web and trace how the WASM full path is converted for the vscode-file:// protocol. Done means the protocol mapping produces the correct local path and the image renders normally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100