You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and several others. Lacking support for these prevents other project from transitioning towards using myst-parser.
e.g. I will not switch over whilst these extensions are unavailable. I am able to achieve more by using restructured text, and these are still able to be used with the sphinx-themes.org themes.
Proposal
The proposal is to add extended support for sphinx extensions to the Sphinx parser in myst-parser.
Tasks and updates
TBD
The text was updated successfully, but these errors were encountered:
Hey @adam-grant-hendry I'm not sure what you mean here; you can use any extension alongside myst-parser, as indeed is the case for the building of the documentation here:
Ah, perhaps I misunderstood: the numpydocs documentation details using rst-style directives, so I wasn't sure if there would be a conflict with using rst-style directives in docstrings if I wanted to use myst-parser syntax in my documentation files...?
One thing for certain that would be excellent is support for adding/specifying 3rd-party MarkdownIt plugins via the conf.py (Issue #632).
Context
Several
sphinx
extensions are used in olderrestructured text
projects, like;numpydoc
sphinxcontrib
and several others. Lacking support for these prevents other project from transitioning towards using
myst-parser
.e.g. I will not switch over whilst these extensions are unavailable. I am able to achieve more by using
restructured text
, and these are still able to be used with the sphinx-themes.org themes.Proposal
The proposal is to add extended support for
sphinx
extensions to theSphinx
parser inmyst-parser
.Tasks and updates
TBD
The text was updated successfully, but these errors were encountered: