Replies: 1 comment
-
It's indeed a feature of Github flavored markdown. But as this is more of a feature request I'm moving this to discussions instead. You can attempt a PR if you want. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description:
After upgrading my app from framework 5.7.29 to 6.18.18, I noticed my email templates that included markdown for strike-through no longer rendered as they did before. The strikethrough wrapper ~~ was passed as-is instead of causing strikethrough.
I believe the source of this issue is the switch to commonmark, and the solution would be as easy as including an option to instantiate commonmark using
new GithubFlavoredMarkdownConverter()
in place ofnew CommonMarkConverter()
Steps To Reproduce:
textBeta Was this translation helpful? Give feedback.
All reactions