Support 'Organize Imports' feature

[akosyakov]

It should:

• remove unused imports;
• remove duplicate imports;
• add imports for unresolved elements;
• ask a user to disambiguous imports in the case if several can be used for an unresolved element.

[basarat]

Personal Opinion: Nice idea for quickfixes / additional refactorings to be added into release 2.1 : https://github.com/Microsoft/TypeScript/wiki/Roadmap#21 🌹

[johnnyreilly]

I'd love to see this implemented.

[akosyakov]

It would be also nice if this feature respects index.ts files and imports stuff with the shortest possible import declaration.

[niklas-dahl]

would be awesome if it could unite imports, too.

from

import { Component } from '@angular/core';
import { Input } from '@angular/core';

to

import { Component, Input } from '@angular/core';

[RyanCavanaugh]

Here's a nice test file https://github.com/Microsoft/vscode/blob/master/src/vs/editor/common/model/editableTextModel.ts

[MgSam]

It would also be great if this feature alphabetized both the objects inside the import {} brackets and the import lines themselves (by file path).

So this:

import { Foo, Bar } from './banana';
import { Dog, Cat } from './apple';

becomes this:

import { Cat, Dog } from './apple';
import { Bar, Foo } from './banana';

[pelotom]

TSLint has a rule for this: ordered-imports. And it’s auto-fixable.

[jbrownson]

It'd be nice if it were inserted in order in the first place so it didn't require the extra auto-fix steps

[madhugb]

Right now sort will put the imports on top of the document, and it moves the comments / copyright / author info to the bottom of imports.

Is there a way to preserve the comments on top of the document?

[amcasey]

@jbrownson, sort on import is covered by #16119.

[amcasey]

@madhugb How are you sorting? I didn't think any of the editors had shipped a version consuming the new organizeImports protocol command.

[amcasey]

@MgSam I believe that was covered by #21909.

[amcasey]

@niklas-dahl I believe that was covered by #21909.

[amcasey]

@akosyakov at present, we're retaining module specifiers as-is. Would you mind filing a new issue suggesting they be simplified when possible?

[amcasey]

Also note that adding missing imports is being handled separately using code fixes (which should support fix-all).

[akosyakov]

@amcasey Are you referencing to shortening imports? As now it works quite nicely for us, except when imports are inserted as . or .., it would be better to ignore index.ts in such cases.