Skip to content

Provide an onTask:foo activation event #126238

Closed

Description

@DanTup

When trying to run a task of type foo when the extension that contributes the relevant task provider not activate the task fails with:

There is no task provider registered for tasks of type "foo"

There's a suggestion at #103942 (comment) that the extension should use an activation event of onCommand:workbench.action.tasks.runTask, but this seems too eager - it will result in the extension being activated for unrelated workspaces and using up resources (eg. spawning language servers, etc.).

I personally find it quite infuriating when I'm working in a workspace of one language type and some random action triggers the activation of a bunch of extensions that do expensive work (for example when the C# extension suddenly activates and starts downloading SDKs, which block some VS Code actions until it completes!). I'd prefer not to have my own extensions have that sort of behaviour.

Activity

  1. vscodebot commented on Jun 14, 2021

    @vscodebot

    (Experimental duplicate detection)
    Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

  2. vscode-triage-bot commented on Jun 15, 2021

    @vscode-triage-bot

    This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

    Happy Coding!

  3. vscode-triage-bot commented on Aug 5, 2021

    @vscode-triage-bot

    This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

    Happy Coding!

  4. DanTup commented on Aug 5, 2021

    @DanTup
    ContributorAuthor

    It seems unlikely this issue is going to get 20 upvotes because a typical user doesn't really understand what this is for. Without this, it's just going to encourage more extensions to eagerly activate and result in other complaints (like performance, or extensions downloading SDKs when they were never supposed to be active, etc. - of which there are already many raised issues).

  5. vscode-triage-bot commented on Aug 16, 2021

    @vscode-triage-bot

    🙁 In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.

    Happy Coding!

  6. alexweininger commented on Sep 4, 2021

    @alexweininger
    Member

    It seems unlikely this issue is going to get 20 upvotes because a typical user doesn't really understand what this is for. Without this, it's just going to encourage more extensions to eagerly activate and result in other complaints (like performance, or extensions downloading SDKs when they were never supposed to be active, etc. - of which there are already many raised issues).

    💯

    This is a much needed feature for extensions that provide tasks.

  7. locked and limited conversation to collaborators on Sep 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions