Closed acnebs closed 2 years ago
Thanks for bringing that to my attention. There was a bug in @lezer/markdown that caused it to drop part of the configuration when multiple aspects were configured. Attached patch (released as 0.15.3) should fix it.
That's great, the syntax highlighting is fixed for me in 0.15.3
. Do you have any thoughts on why my monospace
highlight style isn't being applied when the extensions are functioning?
The parse tree for the code blocks will overlay the CodeText nodes, so you'll get only the highlighting for the inner tree, not the replaced nodes.
Ah gotcha. Yep this seems to be a more complicated problem than I originally expected.
Seems like there was a previous discussion about this for a prior CM version but not for CM6.
Hi, I've found some weird behavior when trying to use Markdown extensions.
Basically, if I use any extension at all alongside the parser, e.g.
Code-blocks within the markdown will no longer be syntax-highlighted. The other strange behavior is that if I apply a
HighlightStyle
which targetstags.monospace
it works when an extension is supplied (i.e. when syntax highlighting is broken) but not whenextensions
is absent.Here is a minimal repro: