-
Notifications
You must be signed in to change notification settings - Fork 27
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
Support Markdown parsing inside collapsible blocks <details><summary>…</summary></details> #5
Comments
@NumesSanguis hello again 👋 of course it's ok to ask for requests here! |
@CrossNox thank you for taking a look at it! Of course you can tag me. Not sure if I can respond quickly due to time-zone differences though. |
This code worked for me in an .rst document (https://stackoverflow.com/a/60394068):
The only caveat is that I have to place |
@NumesSanguis sorry this was kept open for so long. I'm not sure this is relevant to you anymore, but if you could test #35 I'd be very grateful. No problem though if you can't/won't :) |
Hi @CrossNox , thank you for taking a look at it. Unfortunately I'm not working on that project anymore, so feel free to do whatever with this issue. |
Thanks again for m2r2 and I hope it's okay to make requests here?
What I want to do
In my
.md
file I'm making use of collapsible blocks that makes the document much more readable:Which turns on GitHub into:
Expand (CLICK ME)
Large Markdown formatted text:
Issue
When turning the above Markdown into HTML with Sphinx, it just becomes a literal string.
Checking the output of
m2r2 README.md
, we can see that everything is wrapped into a raw html wrapper:Related issue
The problem might be fundamentally the same as encountered by this GitHub Pages user:
https://github.community/t/collapsible-markdown-inside-details-summary-summary-details-fails-to-render/10489
The solution for them was to set a different markdown parser:
markdown: CommonMarkGhPages
Request / Possible solution
<details><summary>
has been used, and only wrap that part into.. raw:: html
ORThe text was updated successfully, but these errors were encountered: