If autoimporting import that is commented out - uncomment it instead of adding new one

Search Terms

autoimport commented uncomment import

Suggestion

Consider we have such imports already in some file:

import React, {
  useState,
  // useEffect,
} from 'react';

Then - if you write useEffect - TS will suggest auto importing it - which is cool. If you choose to auto import it - your import statement will look something like:

import React, {
  useState,
  // useEffect,
  useEffect,
} from 'react';

Which is not a big deal, but leads to some kind of duplication.

Desired result would be:

import React, {
  useState,
  useEffect,
} from 'react';

Which is just removing the comment next to the import I want to use.

Checklist

My suggestion meets these guidelines:

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
• This feature would agree with the rest of TypeScript's Design Goals.

Start in TypeScript's language-service auto-import handling and find the tests covering imports with commented-out named imports. Add a regression case for the shown React-style import and verify that selecting the auto-import removes the comment rather than adding a duplicate import.