Allow files to be excluded from organizeImports

Suggestion

🔍 Search Terms

• organizeImports

✅ Viability 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, new syntax sugar for JS, etc.)
• This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion

I use source.organizeImports as an automated action on save in VS Code. It works great for 99% of my files. However, for some files, it will break my application due to it being destructive. For the 1% of files it will break, I would like source.organizeImports to ignore them.

Would it be possible to add a feature where there is a way to exclude certain files from source.organizeImports to prevent it from running on files it will break?

Thank you!

📃 Motivating Example

In my web application, I have a main.js file that has imports that are not directly used, but needed by other files. The organizeImports feature removes these imports, which breaks my application.

💻 Use Cases

The only workaround for this is to either

• Not automatically run organizeImports on save
• Not edit files that organizeImports will break using VS Code
• Use sortImports and lose the automated cleanup organizeImports provides

None of these workarounds are ideal.

Comienza siguiendo la acción source.organizeImports y cómo selecciona los archivos para la ejecución automatizada; después, revisa el comportamiento existente de sortImports y organizeImports. Define un mecanismo de exclusión para los archivos seleccionados y verifica que los archivos excluidos no se modifiquen, mientras que los demás archivos mantengan el comportamiento actual de limpieza.