markdownDescriptions/markdownEnumDescriptions don't remove ## in settings.json hover

[sean-mcmanus]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.60.0 and 1.61.0-insiders
• OS Version: Windows

Steps to Reproduce:

1. Open settings.json.
2. Hover over some setting like files.autoSave.

Bug: It shows ## still for the command links:

It seems like the ## should be removed if settings.json can't handle it like the settings UI can.

Previously reported as #129844 , but it wasn't fixed (only the settings UI part was).

[roblourens]

I thought there was a version of this open, but I guess it's just the issue you linked, thanks for finding that.

I don't really know what to do about this, I don't think we can actually implement the links in the same way, and the hover here is a generic thing pulling from the JSON schema.

One thing I've thought about is getting rid of the ## requirement, essentially if you have settingName in a description, we could linkify it without requiring special syntax.

[sean-mcmanus]

I assume you mean the setting name would be between the markdown backticks as well (i.e. just the ## would removed). That would require extensions to remove the ## but our extension would be okay with that.

[aeschli]

As you say, the #settingName# notation is only understood by the settings UI. The JSON language server treats this as Markdown that it passes on to the hover.

An idea would be to use the Markdown link syntax similar to command links:. Something like [Editor: Detect Indentation](setting:settingName). It would look nice also in the hover and could bring you to the settings page.

[gjsjohnmurray]

Also happens with markdownDeprecationMessages, though presentation is slightly different, probably because problem hover isn't actually treating it as Markdown.