returns some sort of absolute path depending on environment (i.e. "vscode-file://vscode-app/c:/icons/example.png")
All . / .. relative path indicators are stripped as well (probably for a good reason, maybe not though).
Adding full support for a relative path might introduce the same security blindspot VSCode is avoiding but a couple replacement strings would go a long way into adding more feature-rich descriptions while not having to deal with VSCode's protocol shenanigans.
Having a relative path for markdown images or links would help create nice documentation for local projects. Clickable links, previewable images, etc.
In VSCode, description pop-ups are in a restricted context that doesn't support relative paths.
returns some sort of absolute path depending on environment (i.e. "vscode-file://vscode-app/c:/icons/example.png") All
.
/..
relative path indicators are stripped as well (probably for a good reason, maybe not though).Adding full support for a relative path might introduce the same security blindspot VSCode is avoiding but a couple replacement strings would go a long way into adding more feature-rich descriptions while not having to deal with VSCode's protocol shenanigans.
An alternative solution to this would (and probably the correct one) would be to pass the macroDefinition's description as a MarkdownString so you can set baseUri as the current path.