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

jens1o · 2018-02-11T07:38:31Z

Instead of listening to everything

Lines 21 to 23 in 749536f

    
           "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))

zignd added the enhancement label Feb 12, 2018

jens1o linked a pull request Mar 24, 2018 that will close this issue

Use activationevents to prevent launching the ext on unrelated workspaces #124

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

jens1o commented Feb 11, 2018 •

edited

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

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

Comments

jens1o commented Feb 11, 2018 • edited

jens1o commented Feb 11, 2018 •

edited