Open TylerLeonhardt opened 1 year ago
Describe the bug
👋 from the VS Code team. We noticed that this extension is * activated.
*
When you are * activated, you compete with vscode for start up time and as a result, you hurt vscode's startup time in the process.
It's better to be reactive and only activate when the user interacts with your extension:
To Reproduce Steps to reproduce the behavior:
Expected behavior It shouldn't activate until needed.
Additional context
Activation events for your reference https://code.visualstudio.com/api/references/activation-events
Maybe @c-ryan-k can comment on this?
Describe the bug
👋 from the VS Code team. We noticed that this extension is
*
activated.When you are
*
activated, you compete with vscode for start up time and as a result, you hurt vscode's startup time in the process.It's better to be reactive and only activate when the user interacts with your extension:
To Reproduce Steps to reproduce the behavior:
Expected behavior It shouldn't activate until needed.
Additional context
Activation events for your reference https://code.visualstudio.com/api/references/activation-events