TS auto import should support configuring whether a star or a qualified import is used.

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

[katis]

I would be happy if I could write an item name, find it in the completion list, press <SOME_MODIFIER>+Tab/Enter and have it import the thing as qualified. You could pick the name from file/module the item belongs to, with a kebab-/snakecase converted to camelcase. Rename refactoring could be then used on the qualified name if needed.

i.e.

getName completion could become:

import * as User from `some/module/User`

...

User.getName

[octref]

Copying my original problem here:

For example, now if I type resolve, VS Code auto suggests millions of resolve from all libraries. This is not helpful:

For me, I usually have this

import * as path from 'path'

path.resolve(...)

However now path. doesn’t have any auto import associated with suggestions.

I hope path. can generate completion items that when accepted, add automatic imports to top. The expected behavior is:

• Type path.
• VS Code should auto complete, based on either type definition at @types/node or the Automatic Type Acquisition
• When user accepts path.resolve, add to top of file import * as path from 'path'

---

I think if one types resolve, auto import import { resolve } from 'path' makes sense. However when one types path.resolve, auto import should do import * as path from 'path'.