-
Notifications
You must be signed in to change notification settings - Fork 30.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Activate extension with workspaceContains when a matching file is added to the workspace #28122
Comments
+ broader activation events, since workspaceContains doesn't work as I had hoped (microsoft/vscode#28122)
Are there any plans to implement this? I'd rather not have my extension running permanently to figure out if it can be activated. This would be the far better solution regarding performance. |
As a workaround, you can lazy-load extensions now, so you can lazy load just the detection logic and active that rest on detection change. Ideally this is first party handled by vscode however. |
I was thrown for a loop by the |
@1nVitr0 https://code.visualstudio.com/api/references/activation-events#onStartupFinished
|
@JustinGrote Right, that makes total sense. If combined with the proper |
If I have
"workspaceContains:**/*.md"
as an activationEvent, it would be useful for it to fire when a matching file is added to the workspace, not just when a workspace with matching file is opened.#27665 (comment)
The text was updated successfully, but these errors were encountered: