microsoft / microsoft/TypeScript
Rationalize our presentation and handling of merged/alias symbols in the IDE.
Open
Nobody has claimed this yet.
Domain: API
Domain: LS: Quick Info
Help Wanted
Suggestion
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
Examples of where we could be better:
- Quick info for an alias could present information about the alias, as well as information about what the alias points to.
- Goto-type for a union type could allow you to go to any constituent union-type-element.
- Goto-def on a merged symbol could allow you to go to any declaration.
- Quick info on a merged symbol could show you all the constituent declaration pieces.
etc. etc.
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
Start by reviewing the IDE entry points for Quick info, Goto-type, and Goto-def, then compare how aliases, union types, and merged symbols are represented. Define a separate scope and completion criteria for each behavior before implementation; done should cover the listed navigation and presentation cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100