Extension activates in every VS Code instance - regardless of relevance

[stefan-rooke]

The nextflow extension starts-up in every VS Code instance (new session, new windows) regardless of whether there are any signifiers that the directory contains a nextflow pipeline.

This causes it to spin up a nextflow language server for every local repository I am working on, extending start-up time and leaving unnecessary java processes running, which isn't ideal on our multi-user system.

A downstream effect of this was that it also opened up a welcome page specific to Nextflow every time I opened a project regardless of relevance, which also overode my defaults.
This required me to have to manually reset the default in my user config to prevent welcome pages entirely in order to stop the irrelevant Nextflow welcome pages.

[bentsherman]

That's weird, I thought VS Code extensions only activate when you open a file with a relevant extension. This extension specifies .nf, .nf.test, and .config. Maybe that only triggers the language support.

Thanks for reporting. I'll have to look into the standard practice for starting up an extension conditionally