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
We currently rely on the builtin markdown live preview feature in vscode to render the trace/output. In the future, we should render a webview instead so we have more control over the rendering.
is that we lose support for weird markdown extensions as part of the vscode extensions
full control over the rendering
The text was updated successfully, but these errors were encountered:
Good suggestion! Rendering Markdown in a WebView could provide greater flexibility and customization. However, it's important to consider the potential impact on compatibility with existing Markdown extensions.
To mitigate this, we could work with the Markdown community to identify the most common and useful extensions and ensure they remain supported. Additionally, providing documentation or guidance on migrating from the built-in preview to the new WebView-based one would be helpful for users.
Overall, this is a positive initiative that aligns with our goal of enhancing VS Code's capabilities.
We currently rely on the builtin markdown live preview feature in vscode to render the trace/output. In the future, we should render a webview instead so we have more control over the rendering.
The text was updated successfully, but these errors were encountered: