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
Steps to reproduce the problem (provide example Markdown if applicable):
This is a GFM ~strikethrough~
Expected behavior:
<p>This is a GFM <del>strikethrough</del></p>
Actual behavior:
<p>This is a GFM ~strikethrough~</p>
Notes:
This works fine with double tilde: This is a GFM ~~strikethrough~~ is correctly parsed to <p>This is a GFM <del>strikethrough</del></p>. I'm passing a StrikethroughExtension instance to both the parser and html renderer.
GitHub flavoured markdown supports both double and single tilde strikethrough:
Strikethrough text is any text wrapped in two tildes (~).
To:
Strikethrough text is any text wrapped in a matching pair of one or two tildes (~).
That's a bit annoying. I would normally be hesitant to change behavior of syntax like this now, but given that the aim of the extension is to be compatible with GitHub, I think we should do it anyway. Hopefully no one relies on the previous behavior of single tildes. If they do we can make the behavior configurable via an option later.
Steps to reproduce the problem (provide example Markdown if applicable):
Expected behavior:
Actual behavior:
Notes:
This works fine with double tilde:
This is a GFM ~~strikethrough~~
is correctly parsed to<p>This is a GFM <del>strikethrough</del></p>
. I'm passing aStrikethroughExtension
instance to both the parser and html renderer.GitHub flavoured markdown supports both double and single tilde strikethrough:
~single tilde strikethrough~
:single tilde strikethrough~~double tilde strikethrough~~
:double tilde strikethroughThank you for all your hard work!
The text was updated successfully, but these errors were encountered: