Include directories for nextflow VSCode extension?

Hello,

I am using VSCode for remote development, including nextflow. However, if I connect to my home directory workspace, the nextflow extension will go through my whole home directory and flag ~26k problems after running for a while. This is not great, because I don’t like having >26k problems but also because it takes a couple of minutes to do this after every connect and the extension for example treats every single file that ends in .config as a nextflow config.
Is there a way to have the extension only go through included directories, in addition to the current exclusion list?

Thanks a lot

1 Like

Interesting problem. The best practice with vs code is to use a multi-root workspace rather than opening your entire home directory, and the Nextflow extension is designed to work with that.

  1. Use “Add folder to workspace…” in the command palette to add a workspace root for each Nextflow project you want to have open
  2. Use “Save workspace as…” to save the configuration to a JSON file
  3. Use “Open workspace from file…” to load a workspace from the JSON file
1 Like

Note that the way I personally do this is to launch VS Code from the terminal. I cd to the relevant directory with the workflow and then do vscode . to launch VS Code with that dir as the workspace.

You can also drag + drop directories from Finder / Explorer onto the VS Code app icon to do the same.

Phil

1 Like

Thanks for you feedback, I guess I am using VSCode wrong. I will set up a nextflow workspace as suggested by Ben and disable the nextflow extension for the home directory workspace…
Since I am doing things remotely using vscode . does not really work for me.