They should be relative to the position of the saved VS Code workspace.
So if you do "Save Workspace As" in VS Code, wherever you choose to put that file (We typically do it in the root) of the repo, then it would be relative to that.
Typically we are using this extension with gateways running in docker containers, and not on direct windows installs, so arguably I have not ran through that specific scenario before.
You could try creating a VS Code Workspace in your C:\Program Files\Inductive Automation\Ignition\data directory, and then setting the paths to just be projects?
Or you could try making the workspace in your home directory for your user, and then putting in a full hardcoded projectPath for C:\Program Files\Inductive Automation\Ignition\data\projects? Here is a proposed workspace file for that setup. If you make a folder (wherever you typically use as a working directory, lets pretends its C:\Users\username\ignition
With the file at C:\Users\username\ignition\ignition.code-workspace.json
Could be a designer feature tbh - Visual Studio lets you type cw then tab to auto type console.writeLine(). Would be huge for system.perspective.print().
I use AutoHotKey for that, as well as my Ignition login/pwd. Together they have undoubtedly saved me hours worth of time over just the last couple years.
@thecesrom.git has a set of Python "stubs" that you can import to a modern Python editor corresponding to the system functions:
You will probably still have to manually import systemin your editor to convince it things are in scope. You don't want import system to end up in your final script, though it's not really catastrophic if it does.
From import system many people end up with import MyProjectLibraryScript, which does cause problems [1][2].
It's also unnecessary and can lead to "cargo culting", where people just assume they have to import system for system functions to work, which is not true anywhere [3].