-
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
🔧 MAINTAIN: Support include
parser option in RST
#419
Conversation
Codecov Report
@@ Coverage Diff @@
## master #419 +/- ##
==========================================
+ Coverage 90.67% 90.77% +0.09%
==========================================
Files 14 16 +2
Lines 1855 1875 +20
==========================================
+ Hits 1682 1702 +20
Misses 173 173
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Note, this is not really the intended use case of myst_parser, so I won't be officially supporting it, i.e. if it does not work for whatever reasons, I won't treat that as a bug |
include
parser option in RST
Thanks! Question about your last comment: is building with Sphinx the only supported use case, or is the plan to also support building with the standard Docutils pipeline? (or in fact with other programs that build on top of it, like Pelican?) The reason I'm asking is that I use the standard Docutils pipeline in plenty of places, and I wouldn't be against migrating these documents to Markdown — but I want to make sure that things aren't going to break unexpectedly. |
Cc @damianavila who was playing around with getting Myst to work in Nikola |
I think we would be super nice to be able to use MyST with docutils — the way reCommonMark can be used and through the usual methods in |
supercedes #414
cc @cpitclaudel
closes #417
closes #388