Support ${workspaceFolder} in includePaths and linterExtraArgs

[dnwillia-work]

This variable is supported by other code parsers (eg: C++ parser from Microsoft). It would be great if it was working since it allows teams using VS code to keep a single project settings.json file in the git repo and have team members clone to wherever they like. For example:

"fortran.includePaths": [
  "${workspaceFolder}/myincludes",
  "${workspaceFolder}/mymodules" ],
"fortran.linterExtraArgs": [
  "-J${workspaceFolder}/mymodules"]

then it would just work.

Looks like maybe a straightforward change here at the bottom of the file?

[pedro-ricardo]

That's a good suggestion 👍
I'll need to search for a reference in other extensions to know how to interpret the sting and get that ${workspacePath} value.
Doesn't sound complicated.

[dnwillia-work]

Great, thanks. Seems I made a mistake though, the correct variable is ${workspaceFolder}. I've updated the title and my opening post.

[dnwillia-work]

Looking at this link seems what you want is vscode.workspace.workspaceFolder[0]

[nyckmaia]

The variable "${workspaceFolder}" is now working in "fortran.includePaths".

Is the a solution?

[gnikit]

As far as I can tell, for this to be functional and general a bit more work will need to be done since the paths in includePaths would still need to be resolved for ${workspace} variables, similarly to how it is done in the C++ extension.
Same applies for linterExtraArgs.

I see what I can come up with although I will admit that TypeScript is not my strong suit

[gnikit]

This is now in v2.6.1 available in the VS marketplace. Also glob patterns in include paths are now supported but be careful not to give overly general globs because gfortran has a limit to the number of arguments it can have during compilation.