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
Hey @nartc I have been relying heavily on notion-stuff for a recent project. It's great!
I ran into an issue with the blocks-markdown-parser where a toggle block with a code block nested inside of it (pretty common use case to represent JSON or something) will get rendered incorrectly. The problem is that anything nested inside a valid html tag gets skipped by marked. When toggle content is wrapped in details tags, the code block is left as a string. This would be a problem for anything the parser wraps inside of tags.
You can see exactly what I'm talking about in the official marked demo here.
Do you know any way around this? The only fix I can think of is to run marked to eagerly convert the markdown into html. Is there something to be done at the marked config level? I noticed that in the demo it worked closer to expected in the "daring fireball" flavor.
Happy to contribute if we can come up with a good fix.
The text was updated successfully, but these errors were encountered:
Hey @nartc I have been relying heavily on notion-stuff for a recent project. It's great!
I ran into an issue with the
blocks-markdown-parser
where a toggle block with a code block nested inside of it (pretty common use case to represent JSON or something) will get rendered incorrectly. The problem is that anything nested inside a valid html tag gets skipped bymarked
. When toggle content is wrapped indetails
tags, the code block is left as a string. This would be a problem for anything the parser wraps inside of tags.You can see exactly what I'm talking about in the official
marked
demo here.Do you know any way around this? The only fix I can think of is to run
marked
to eagerly convert the markdown into html. Is there something to be done at themarked
config level? I noticed that in the demo it worked closer to expected in the "daring fireball" flavor.Happy to contribute if we can come up with a good fix.
The text was updated successfully, but these errors were encountered: