Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TypeScript organize imports doesn't match TSLint ordered-imports #30722

Closed
jritzi opened this issue Apr 2, 2019 · 2 comments
Closed

TypeScript organize imports doesn't match TSLint ordered-imports #30722

jritzi opened this issue Apr 2, 2019 · 2 comments
Labels
Duplicate An existing issue was already created

Comments

@jritzi
Copy link

jritzi commented Apr 2, 2019

Issue Type: Bug

We use TSLint's ordered-imports rule to enforce alphabetized imports in TypeScript, and in general VSCode's organize imports feature adjusts the order correctly. However, I've run into a problem with the following example:

import {
  OutputInfo,
  OUTPUT_INFO_STORE,
} from 'output-info';

TSLint complains that those imports are out of order, and a JetBrains IDE correctly switches those two when organizing imports. However, VSCode leaves it as shown above (and reverts to that order if I manually swap them). This happens running TypeScript 3.3.3 in VSCode 1.32.3.

VS Code version: Code 1.32.3 (a3db5be9b5c6ba46bb7555ec5d60178ecc2eaae4, 2019-03-14T22:46:48.547Z)
OS version: Darwin x64 17.7.0

@vscodebot vscodebot bot assigned mjbvz Apr 2, 2019
@mjbvz mjbvz transferred this issue from microsoft/vscode Apr 2, 2019
@mjbvz mjbvz removed their assignment Apr 2, 2019
@RyanCavanaugh
Copy link
Member

Duplicate #30430

@RyanCavanaugh RyanCavanaugh added the Duplicate An existing issue was already created label Apr 2, 2019
@typescript-bot
Copy link
Collaborator

This issue has been marked as a 'Duplicate' and has seen no recent activity. It has been automatically closed for house-keeping purposes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Duplicate An existing issue was already created
Projects
None yet
Development

No branches or pull requests

4 participants