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
Second I though it would probably be better to ignore HTML comments within the markdown text, for example I have an automatic TOC generator that will wrap the generated (nested) list into HTML comments, that will end up like this after parsing:
Tried to fix that, but my regex skills are not good enough I guess... I would assume some kind of negative lookahead or negative lookbehind (can we use that outside of node though?) could do that when combined with ((.|\n)+?)(\n\n+|$), but I couldn't figure it out...
First of all, amazing work you have done here!
Second I though it would probably be better to ignore HTML comments within the markdown text, for example I have an automatic TOC generator that will wrap the generated (nested) list into HTML comments, that will end up like this after parsing:
not a big deal, but you'll get some extra spacing because of that.
The text was updated successfully, but these errors were encountered: