Allow configuring a base uri for MarkdownString

[mjbvz]

Feature request

Allow configuring a base uri that is used when rendering the contents of a MarkdownString. This uri would be used when resolving relative paths that appear as links or image links within the markdown string

Example use case

const md = new vscode.MarkdownString(`
[link](toSiblingFile.md)

![img](./image/from/dir.gif)
`);

md.baseUri = vscode.window.activeTextEditor.document.uri

When rendered, link and img should both resolve to files next to the currently active file

Related issues

• "Error: Unable to resolve non-existing file" on JSDoc file link #130968
• Support local paths in hover MarkdownString #86564

[mjbvz]

The alternative today is that extensions have to parse the markdown and transform the uris themselves. This is difficult to get correct

[DanTup]

@dbaeumer is this something that should be in the LSP spec (for servers to set), or the client (assuming they should be relative to the document the request relates to)?

[dbaeumer]

@DanTup I think we should do the following:

• spec that a markdown string in a response can have relative links based on the requesting document
• set the base in the VS Code lsp client.