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
Currently there are three separate, partially implemented markdown renderers in the Zed codebase:
rich_text::RichText, used by the markdown renderer and chat messages, specialized to support @mentions and style code blocks, caching, doesn't support inline code regions (the `)
markdown_renderer::Render, used by the markdown renderer, supports blocks like lists, tables, and headlines, non-caching
language::markdown, used by the editor popovers, provides caching, supports inline code regions and lists.
These implementations have been developed organically and are specialized to their use cases. We should be intentional about what parts of this we unify and which we leave separate. But that said, it would be nice to:
Ensure that all normal markdown syntax is supported everywhere (inline-code blocks)
Support fancy markdown tables and such in the channel chat, because it's fun
Have all markdown parsing be cached by default
Regardless of how that effort turns out though, inline-code blocks not rendering in the markdown preview is a bug, and should be fixed.
Currently there are three separate, partially implemented markdown renderers in the Zed codebase:
rich_text::RichText
, used by the markdown renderer and chat messages, specialized to support @mentions and style code blocks, caching, doesn't support inline code regions (the `)markdown_renderer::Render
, used by the markdown renderer, supports blocks like lists, tables, and headlines, non-cachinglanguage::markdown
, used by the editor popovers, provides caching, supports inline code regions and lists.These implementations have been developed organically and are specialized to their use cases. We should be intentional about what parts of this we unify and which we leave separate. But that said, it would be nice to:
Regardless of how that effort turns out though, inline-code blocks not rendering in the markdown preview is a bug, and should be fixed.
Reproduction steps:
inline code block
The text was updated successfully, but these errors were encountered: