Skip to content

Use activiation events to prevent running the extension on unexpected workspaces #116

Open
@jens1o

Description

@jens1o

Instead of listening to everything

"activationEvents": [
"*"
],

we could use something like:

 "activationEvents": [
    "onLanguage:css",
    "workspaceContains:**/*.css"
],

which will only start the extension when there are css files on the entire workspace(including subfolders) or a css file is going to be created.

This will save memory and unneeded cpu usage.

(extracted from #114 (comment))

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions