Microsoft/TypeScript

Import auto-import doesn't take into account the current import statement

Open

#52.788 geöffnet am 15. Feb. 2023

Auf GitHub ansehen
 (0 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)TypeScript (6.726 Forks)batch import
Experience EnhancementHelp WantedSuggestion

Repository-Metriken

Stars
 (48.455 Stars)
PR-Merge-Metriken
 (Durchschn. Merge 6T 17h) (9 gemergte PRs in 30 T)

Beschreibung

Bug Report

🔎 Search Terms

  • import
  • auto-import

💻 Code

Use Visual Studio for the following:

  1. In file1.ts, write export zero = 0;
  2. In file2.ts, write import ze and notice the completion entry for zero.

🙁 Actual behavior

If the completion entry for zero is selected, the contents in file2.ts will be replaced by:

import { zero } from "./file1.ts";
import z

After discussing the bug with @andrewbranch, he pointed out how this is the correct behavior because the entry that VS is showing corresponds to an auto-import.

🙂 Expected behavior

The auto-import completion entry shouldn't show up if the current line corresponds to an import statement itself (in case the editor doesn't have preferences.includeCompletionsForImportStatements and preferences.includeCompletionsWithInsertText set).

Contributor Guide