Allow MarkdownStrings to be an option for QuickPickItem's detail, label and description.

[PizieDust]

The label, detail and description fields of QuickPickItems only accepts Plaintext. It will be nice to have markdown support as sometimes some of these fields can be code syntax.

Broadly and ideally it will be great to have markdown support for all descriptions and similar fields which accept plaintext.

cc @xvw @voodoos

[vs-code-engineering[bot]]

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[TylerLeonhardt]

I think we have to be careful here. For Quick Pick we don't want to support headings because we want things to look consistent.

• bold
• italics
• code (inline)
• stikethrough
• (maybe) links

and other inline syntaxes make sense... but headings, images and other things that would affect the height of the container don't make sense IMO.

So does MarkdownString make sense for a subset of features? Or should it just be supported via strings... kinda like we have already for notification links, I believe.

[PizieDust]

Yes the subset you have mentioned seems very reasonable. What is the conventional way to implement this? Via MarkdownStrings or added support for strings?

[TylerLeonhardt]

I think I lean MarkdownString...