Beginnings of experimental MyST support #54
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I had a grand vision of fully supporting both MyST and Djot syntax, since MyST has a much better role/directive feature.
Unfortunately, I found huge gaps in the JS implementation of
myst-parser
. I also don't like that it seems to be built on top ofmarkdown-it
, but then provides a data structure that is part of a completely different project (remark
). And a fewmyst-parser
dependencies pin old versions ofmarkdown-it
which trigger noisy deprecation warnings. Overall not ready for prime time.That said, I'm not going to toss out all the work because it looks like adding
remark
support is probably the way forward. Then I can ditch thepandoc
requirement for GFM and useremark
extensions instead, and usemdast
internally instead of the Djot AST, which has a lot of nice utilities available and is more syntactically rich.