search

broadinstitute / wdl-ide

Rich IDE support for Workflow Description Language
BSD 3-Clause "New" or "Revised" License
40 stars 8 forks source link

Need to be able to set project base for imports #7

Open GregTD42 opened 4 years ago

GregTD42 commented 4 years ago

Using this within Visual Source Code

Within my VSC root directory I have 4 projects: Pipeline, Utils, Upload, and Download

I am required to have the import path of the files in pipeline be Pipeline/src/wdl/... If I import a file from Utils its path is Utils/src/wdl/...

So far as this tool is concerned, none of my imports are valid, so utilities like "Show Definition" do not work.

I need a parameter I can set in the .env files that lets me tell the WDL tools where the project base (or bases) is for imports

dinvlad commented 4 years ago

Thanks for raising the issue @GregTD42 !

The existing logic to resolve WDL paths goes as follows: 1) If multiple "workspace folders" feature of VC Code is used, then it crawls each such folder. 2) If "workspace folders" is not used, and only a single "root folder" is opened in VS Code instead, then it crawls that folder.

So from what I can see, it should correctly resolve any WDL paths in either case, as long as all of the WDLs are located within the same workspace (i.e. either a "workspace folder" or a "root folder"). Does that make sense?