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
Hi, I'm on the vs code team. We recently introduced a more standardized way to implement Organize Imports with code actions (microsoft/vscode#47845). Using code actions instead of commands allows vs code to provide a more standard and consistent experience across languages. We are also using the new code action based implementation to power new UI like the Source Action context menu
Our JavaScript and TypeScript organize imports feature has already been migrated from a command to a code action: microsoft/vscode#46647 I suggest that the Java extension do the same so that the developer experinace is more consistent and to prevent conflicts with other extensions. This is currently blocked by microsoft/language-server-protocol#389
The text was updated successfully, but these errors were encountered:
Hi, I'm on the vs code team. We recently introduced a more standardized way to implement
Organize Imports
with code actions (microsoft/vscode#47845). Using code actions instead of commands allows vs code to provide a more standard and consistent experience across languages. We are also using the new code action based implementation to power new UI like theSource Action
context menuOur JavaScript and TypeScript organize imports feature has already been migrated from a command to a code action: microsoft/vscode#46647 I suggest that the Java extension do the same so that the developer experinace is more consistent and to prevent conflicts with other extensions. This is currently blocked by microsoft/language-server-protocol#389
The text was updated successfully, but these errors were encountered: