-
Notifications
You must be signed in to change notification settings - Fork 110
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simply thank you! #217
Comments
Also, I have a question: how do you recommand to handle malformed Markdown? |
Hi @Lucas-C, thanks for your message, I guess it would make @miyuchina happy, provided he still watches this project. :) To your question, I think the common approach so far is to skip the "malformed markdown" and treat it as it would be a plain text instead - as it actually could be just a text. At least that is what I can see in the various examples in the CommonMark spec. But I would also say it also depends on the exact case we want to handle. So your suggestions could possibly be also valid, but I'm not just sure at the moment... |
@Lucas-C thank you also for providing this example for a custom block token - I found it really helpful! Perhaps it could be a good idea to add this example to the developer guide, so that there is one example for a span token and one for a block token? |
Hi!
I just want to report a happy user 馃檪
I have switched from using
markdown-it
(NodeJS) tomistletoe
, and I really love it.This morning, in 30min, I was able to quickly add support for
:::
block containers, in a similar fashion as markdown-it-container:Example Markdown content that can be processed by this parser:
The API of your library is really well crafted,
and its excellent design makes it very easy to extend!
So I just wanted to say THANK YOU 馃憤
The text was updated successfully, but these errors were encountered: