microsoft / microsoft/TypeScript
Make automatic adding missing imports smarter
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
Scenario 1: Fuzzy Logic
I have a several files containing import {connect} from "react-redux";. If I use the add missing imports context menu to add the missing import for connect, the system should realize "react-redux" is far more probable module than "net", "tls", and "http2", which are all recommended higher than "react-redux", but none of which are used anywhere in my project.
Scenario 2: Respect node conventions
If I have a file ./myfolder/index.ts, I can import the file with import "./myfolder". The system currently resolves missing imports from ./myfolder as ./myfolder/index.ts, when it should actually use ./myfolder.
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 both scenarios with the TypeScript files described: a missing react-redux connect import and an import from ./myfolder where index.ts is the entry point. Start by locating the add-missing-imports and module-resolution paths, then verify that project usage affects ranking and that the directory specifier is preserved. Done means both scenarios choose the expected import forms without regressing existing suggestions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100