Support relative paths for markdown images in doc comments

[jifalops]

I'm trying to have an image appear for each IconData in our icon font, similar to Icons.foo in Flutter.

I finally got the images generated from the .ttf file, but they only show correctly in the doc-comment-popup if it uses an absolute path to the image, which means it won't work for anyone else.

// Works
/// ![icon](/home/jacob/the_project/doc/icons/icon.png|width=32,height=32)
static const icon = IconData(\x0000, fontFamily: 'MyFont');

// Does not work
/// ![icon](doc/icons/icon.png|width=32,height=32)
static const icon = IconData(\x0000, fontFamily: 'MyFont');

I have tried relative paths:

• plain (like above)
• with leading ./
• with leading / (html style)
• using .../../.. as necessary to navigate from the file to the root of the project
• using <img src="">

[DanTup]

Thanks for the report! The markdown here is rendered by VS Code, so this would be best fixed there (the same bug exists in other languages - the relative path is resolved from the VS Code application folder). I've opened an issue you can put a 👍 on here:

microsoft/vscode#95947

[DanTup]

The VS Code issue was closed as a dupe of microsoft/vscode#86564. I'll close this as a dupe too, as I believe once fixed in VS Code, it'll just work here. Thanks!

[DanTup]

I suspect this won't get done without a contribution to the VS Code LSP Client, so re-opening this as a placeholder/reminder.