microsoft / microsoft/TypeScript
ctrl+click on an existing asset with a querystring
Open
Nobody has claimed this yet.
Experience Enhancement
Help Wanted
Suggestion
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 117
Description
Does this issue occur when all extensions are disabled?: Yes/No
- VS Code Version: 1.80.0
- OS Version: macOS latest
Steps to Reproduce:
- write
import foo from './existing-file.js?some-query-string' - ctrl+click on the file path
Expected
VSCode opens the file as if there was no querystring
Actual
Either:
- VSCode complains with:
cannot find module './existing-file.js?some-query-string' or its corresponding type declarations - if there's a
.d.tswithdeclare module '*?some-query-string' {}, VSCode will navigate to this particular declaration block
Contributor guide
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
Reproduce the behavior with the import and ctrl+click steps in the issue, then trace TypeScript's editor navigation for module specifiers containing query strings. Done means an existing asset opens normally without the query string, rather than producing a missing-module error or navigating to a wildcard declaration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100