microsoft / microsoft/TypeScript-Sublime-Plugin
Go-to-def should behave the same way as find-all-refs when there are multiple definitions
Open
Nobody has claimed this yet.
Enhancement
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 236
- Avg merge
- 21d 13h
- Merged PRs (30d)
- 1
Description
For instance, go-to-def on Array should give both its constructor-side declaration as well as the interface Array<T>.
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 tracing the plugin's go-to-definition handling and comparing it with the find-all-references path described in the issue. Verify the behavior for Array; done means go-to-def returns both the constructor-side declaration and the Array<T> interface, with the relevant tests updated or added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- devtools, search
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100