You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
use setTimeout in a large javascript file that didn't use it before.
import { setTimeout } from "timers"; is added to top of file, without any notification, question, prompt, warning, or visible change on screen.
This is an absolutely terrible default, it's unclear the change to my code is happening, as it's not even visible on the screen. It breaks my code. Like most people, I am migrating to TypeScript, not using it exclusively. Some of my code is not compiled before being shipped. This just confuses browsers, and I don't want it.
This whole feature should be removed until a better UX can be implemented. As a general rule, a code editor doesn't mess with code like this. It isn't your job to be writing my code for me. If I wanted this thing to behave like an IDE, I'd use an IDE. This behavior change is entirely unexpected for an editor. It breaks our workflow. Either ask me before making changes, or stop making changes I can't see.
The text was updated successfully, but these errors were encountered:
As already covered, you can disable this by setting: "typescript.autoImportSuggestions.enabled": false. If you are seeing bugs with auto-import behavior or have ideas on how the UX could be improved, please file new issues
Steps to Reproduce:
import { setTimeout } from "timers";
is added to top of file, without any notification, question, prompt, warning, or visible change on screen.This is an absolutely terrible default, it's unclear the change to my code is happening, as it's not even visible on the screen. It breaks my code. Like most people, I am migrating to TypeScript, not using it exclusively. Some of my code is not compiled before being shipped. This just confuses browsers, and I don't want it.
This whole feature should be removed until a better UX can be implemented. As a general rule, a code editor doesn't mess with code like this. It isn't your job to be writing my code for me. If I wanted this thing to behave like an IDE, I'd use an IDE. This behavior change is entirely unexpected for an editor. It breaks our workflow. Either ask me before making changes, or stop making changes I can't see.
The text was updated successfully, but these errors were encountered: