Errors contain aboslute path to affected file

[CodingMarkus]

Errors contain aboslute path to affected file

[bscan]

Hi @CodingMarkus, thanks for the report. Which editor and Navigator version are you using? This should've been fixed in January for the currently active file e0e119f

See example below, where a syntax error in the currently active file does not display the path.

The Navigator has code to "localize" errors as well. If a loaded module throws an error or a warning, it will try to display that diagnostic on the line where the module is imported (e.g. Foo's warnings are shown on the use Foo line). However, I like the idea of displaying a project relative path when possible. If a file path starts with a workspace path, it would be nice to strip that part out. This won't always work, as there will still be cases where other dependencies outside of the project will throw errors.

[CodingMarkus]

Ah, my bad. I got it from here

https://open-vsx.org/extension/bscan/perlnavigator

so I assumed that is the latest version available, after all it seemed you have published it there yourself. I'll try the latest release instead.

[CodingMarkus]

You are correct, is fixed.

My apologies again, I should have first checked if that is really the latest version.

[bscan]

Thanks, I just published the latest version to the Open-VSX store. Currently, there is a Github action that publishes automatically to the npm registry, but I need to manually publish to the vscode Marketplace and the Open-VSX Marketplace. Thank you for the report.