Relative path of images supported in .xsd file?

[sreensr]

![text] (absolute/path/to/image.png)" in xsd file works and image is visible when hover over the respective value.
Unfortunately the ![text] (relative/path/to/image.png)" dosen't works. Is this a known issue?

[angelozerr]

Could you add a sample please.

[sreensr]

Sure. The following lines in .xsd file gives me the result as expected. Here I have used the absolute path of the imge. So when I hover over "Minion" I could see the image.

Unfortunately, when relative path of image is provided, result is not as expected and image is not visible when I hover over the corresponding value as shown in the picture below

My folder structure is:

.xsd file is inside the language_definition folder

[fbricon]

can you attach your test files here please?

[angelozerr]

@sreensr tobe honnest with you I didn't know that we support hover image like yoiu did.

Our hover doesn't update the content of the documentation before returning. We take the content as is and convert it to markdown.

To fix our issue we should pre process the uri of the markdown image.

[sreensr]

can you attach your test files here please?

Sorry I won't be able to attach test files. It's confidential

[fbricon]

Surely you can come up with a simple, non-confidential test file.

[angelozerr]

@fbricon we don't do some process for documentation, in other words we return to vscode the content ![text] (absolute/path/to/image.png) which is a markdown syntax and it is vscode which renders the markdow.

To fix this issue we need to parse documentation content and update the relative path, it means that we need to implement a simple a Markdown parser which process Markdown link.

The only process that we do is to convert HTML to Markdown if the documentation uses HTML.

[fbricon]

Yes I was looking into it. The problem is passing the current path to the markdown processor will be a bit convoluted.

[angelozerr]

The first step that we could manage is to support relative path by writing html doc instead of markdown since remark have a convert with baseuri

[fbricon]

the fact markdown format seems supported in XSD documentation is a fluke. Given we need to replace the HTML->Markdown conversion library (we're also affected by eclipse-jdtls/eclipse.jdt.ls#2957), it most likely will stop working.

Writing HTML documentation (with <img src="") is probably safer

[sreensr]

The first step that we could manage is to support relative path by writing html doc instead of markdown since remark have a convert with baseuri

Because of some reason, the html version <img src="" simply doesn't works for images saved locally. And that's why I ended up using the markdown.

[angelozerr]

We need to investigate why it doesnt work but @fbricon is working to change the html > markdown converter library. Perhaps it will work better?

In short please dont use markdown.

[jtschea]

Dear vscode-xml-Developers,

I would be also interested in this feature. Just to emphasize that again, even if only using <img src=.../> it is just working for http/https but not for file URLs.

When being used with file URL the result is as follows:

Result: {
    "contents": {
        "kind": "markdown",
        "value": "# ![Image]()\n\n#\n\nSource: [my.xsd](file:/path/to/my.xsd)"
    },
    "range": {
        "start": {
            "line": 20,
            "character": 42
        },
        "end": {
            "line": 20,
            "character": 79
        }
    }
}

In contrast to using http/https the generated Markdown does not have a valid path ![Image]().

Do you know a way to work around this?

Best regards and thanks in advance,
Jupp