microsoft / microsoft/TypeScript
Using VS Code Go to Declaration support
Open
Nobody has claimed this yet.
Domain: LS: Symbol Navigation
In Discussion
Suggestion
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
VS Code 1.30 adds support go to declaration. This supplements the existing go to commands we already have for TypeScript:
go to definitiongo to type definitiongo to implementation
Although this was added mainly to support languages like C++, I wonder if typescript tooling could also use go to declaration. Some ideas:
- https://github.com/Microsoft/TypeScript/issues/14588
- Going to the
d.tsfile (even if declaration map file exists)
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
Read VS Code 1.30's go-to-declaration behavior and the linked TypeScript issue 14588 first. Compare it with the existing go-to-definition, go-to-type-definition, and go-to-implementation commands, including the stated .d.ts target idea. Done means TypeScript tooling supports the requested go-to-declaration behavior with agreed navigation semantics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100