microsoft / microsoft/TypeScript
Annoying completions, where only `extends` keyword is expected
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.4k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 117
Description
Bug Report
From the following bug reports:
- https://github.com/microsoft/TypeScript/issues/53467
- https://github.com/microsoft/TypeScript/issues/53372
After interface Foo or generic TypeScript doesn't suggest just extends keyword, instead, it just doesn't block completions now. I wonder is this possible to complete only valid extends keyword instead of showing everything? For example variables previously were not suggested:
cc @a-tarasyuk
Again, I'm not against new behavior, just wondering wether the fix can be improved
Please fill in each section completely. Thank you!
-->
🔎 Search Terms
extends other completions
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 completion behavior after an interface declaration and after a generic, using the linked reports for comparison. Trace the TypeScript completion entry point and identify the relevant tests; done means valid positions suggest extends without the unrelated completions described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100