-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade Marked (or switch to a different Markdown implementation) #272
Comments
Aside: I originally intended to have two separate lists. In marked up until version 3.0.0 this can be achieved by separating the lists with two newlines. From version 3.0.0 and onward marked follows commonmark, which requires a hack to separate the lists. |
We can’t upgrade Marked (used by our |
I have a few more weird behaviors…
produces this HTML code (second line ignores the italics): <p><em>Underscore italics</em></p>
<p>_Underscore italics with <code>a_variable_name</code> embedded_</p> This works correctly when using asterisks instead of underscores. This code
produces this output (backticks are sometimes ignored): <p>Here are escaped backticks `md`, and here they are un-escaped inside a code block: `md``` hello</p>\n<p>But they work when there's a space: <code>md``</code> back to normal</p> The backtick issues are fixed in the current version, but the underscore confusion seems to persist (but looks a little different). See this test in the Marked playground. |
Another one, which is resolved in newer version of marked:
Should be:
|
Given the following Markdown containing a "loose list":
the generated HTML wraps multiple elements in paragraphs:
resulting in the following appearance:
Observable currently uses marked 0.3.12. This bug got fixed in marked 0.5.0 (demo, PR).
The text was updated successfully, but these errors were encountered: