-
Notifications
You must be signed in to change notification settings - Fork 197
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
No longer a canonical way to parse a simple snippet #879
Comments
Thanks for opening your first issue here! Engagement like this is essential for open source projects! 🤗 |
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? |
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 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! :) |
@rowanc1 thanks, that makes sense! Sorry, I overloaded this issue but my primary question was what I should now use for |
Describe the gap in the current documentation
Old docs used to have the following, but I cannot find the new equivalent
Describe the solution you'd like
Documnetation covering how to parse myst for simple usages i.e.
display(HTML(parse_myst_to_html(markdown)))
The text was updated successfully, but these errors were encountered: