You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I work on the commenting API in VS Code, and I'm opening this issue because this repository contains usages of the commenting API.
We recently noticed that even though a Comment's body can be string | MarkdownString we're always displaying it as a MarkdownString (issue). The upcoming 1.64 release will fix that: when a comment body is a string it will be displayed as a plain string and not as markdown. As a user of the the commenting API, this project may be affected by this.
If this project does wish to keep displaying comment body as Markdown, simply create a new MarkdownString and use that as the comment body:
comment.body=newvscode.MarkdownString(body);
It's also possible that this project doesn't rely on the incorrect display behavior and that this issue can be disregarded!
The text was updated successfully, but these errors were encountered:
Hello 👋
I work on the commenting API in VS Code, and I'm opening this issue because this repository contains usages of the commenting API.
We recently noticed that even though a
Comment
'sbody
can bestring | MarkdownString
we're always displaying it as aMarkdownString
(issue). The upcoming 1.64 release will fix that: when a commentbody
is astring
it will be displayed as a plain string and not as markdown. As a user of the the commenting API, this project may be affected by this.If this project does wish to keep displaying comment
body
as Markdown, simply create a newMarkdownString
and use that as the comment body:It's also possible that this project doesn't rely on the incorrect display behavior and that this issue can be disregarded!
The text was updated successfully, but these errors were encountered: