Navigation to definition or references fails on Windows

[HughG]

I'm using extension version 0.2.1, VSCode version 1.78.2, on Windows 10.

I'm not able to jump to definitions or references from a need ID in an option like links. Due to #26 my configured workspace paths are using relative paths like source and build/needs/needs.json, without ${workspaceFolder}. It may be that this issue would be fixed if #26 were fixed.

If I add ${workspaceFolder}, I get errors like the following in the extension's output, and there's nothing from the extension UI for hover or navigation.

[Error - 13:26:46] Given needs.json not found: /c%3A/Projects/Personal/sphinx-needs-vscode-ext-play/build/needs/needs.json
[Warn - 13:26:48] No needs info extracted from needs json. No completion feature.
[Warn - 13:26:51] No needs info extracted from needs json. No Hover feature.

If I leave out ${workspaceFolder} then, for a file in <my_workspace>/source/foo.rst, VSCode tries to open \source\foo.rst. As you may know, on Windows this means X:\source\foo.rst where X is the current drive of the VSCode process.

[danwos]

A fix may need some time, as we all have Linux machines here.
But the problem sounds like a standard path problem to solve. So not too difficult.

[HughG]

@danwos, as you can see, I have a lead on fixing this proble: using the vscode-uri extension.

After this change, the explorer view is also broken for me, but that may well be because I'm doing something wrong in terms of setup for VSCode extension development, since it's not something I've done before.

I'm not likely to do any more work on this now because I'm looking into using Logseq for Planguage requirements instead. Thanks for your quick response at the time, though!

[melund]

@danwos We have also run into this issue. All my colleges are exclusive on Windows. I haven't got any vscode-extension or typescript skills, so I may not be able to fix this my self. But if I can help test any fixes then let me know.