Microsoft/TypeScript

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

Open

#52 788 ouverte le 15 févr. 2023

Voir sur GitHub
 (0 commentaires) (0 réactions) (0 assignés)TypeScript (6 726 forks)batch import
Experience EnhancementHelp WantedSuggestion

Métriques du dépôt

Stars
 (48 455 stars)
Métriques de merge PR
 (Merge moyen 6j 17h) (9 PRs mergées en 30 j)

Description

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).

Guide contributeur