No longer a canonical way to parse a simple snippet about myst-parser HOT 4 OPEN

Thanks for opening your first issue here! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out EBP's Code of Conduct. Also, please try to follow the issue template as it helps other community members to contribute more effectively.

If your issue is a feature request, others may react to it, to raise its prominence (see Feature Voting).

Welcome to the EBP community! 🎉

from myst-parser.

Different question – mystmd and myst-parser docs differ in places (https://mystmd.org/guide/code#numbering-and-highlighting vs https://myst-parser.readthedocs.io/en/latest/syntax/code_and_apis.html#adding-a-caption) . I was hoping these would be consistent flavors I could use across notebooks, frontend apps, etc. Are these docs out of date or just a hiccup/slight out-of-sync state between the libraries?

from myst-parser.

The goal of MyST as a markup language is to be consistent across various implementations (sphinx, python, javascript, etc.). In this specific case, we actually are, I think (with the exception of the force flag), the full directive docs for mystmd are here (the example is different):
https://mystmd.org/guide/directives#directive-code

Hope that helps @micimize! There are certainly other places where there are inconsistencies between these implementation and documentation. We are continually trying to improve it, so if you see something, please let us know! :)

from myst-parser.

@rowanc1 thanks, that makes sense! Sorry, I overloaded this issue but my primary question was what I should now use for parse_myst_to_html for a use-case like display(HTML(parse_myst_to_html(markdown)))

from myst-parser.