microsoft / microsoft/TypeScript
TS auto import should support configuring whether a star or a qualified import is used.
Open
Nobody has claimed this yet.
Awaiting More Feedback
Suggestion
VS Code Tracked
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
From @dbaeumer on October 31, 2017 11:29
Testing: #37177
- vscode source code opened in VS Code
- open a file that doesn't import
'vs/base/common/types' - type isStringArray
- select the entry from code complete list
- the following import is inserted:
import { isStringArray } from 'vs/base/common/types';
However what I want in this case is
import * as Types from 'vs/base/common/types';
and the code should become Types.isStringArray
Would be cool if I can control this via a setting.
Copied from original issue: Microsoft/vscode#37258
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 reported auto-import completion in a VS Code source file using the isStringArray example, then trace the TypeScript auto-import completion behavior. Define how a setting would choose named versus namespace imports and verify that the selected style also changes the resulting reference to Types.isStringArray.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100