-
Notifications
You must be signed in to change notification settings - Fork 196
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
Translate non-default directives (breathe extension) #323
Comments
As with #322, this seems to be something to be an issue specific to https://github.com/michaeljones/breathe and the way it works in registering directives: https://github.com/michaeljones/breathe/blob/4ce8c7a0d79f79f0ae3e7c7fbaa9c4fbb5c84888/breathe/directives.py#L564-L573 There is usually just a simple cache linking directive names to directive classes, but it seems that what happens if you do: ```{eval-rst}
.. doxygenstruct:: MyStruct
``` |
yes, that works. Actually, that works for me. Breathe directives are so far away from anything that is Markdown, so it's fine to put them in a code fence. |
ah good to hear 👍 it would be nice to get to the bottom of why breathe seems to "break" myst-parser, but indeed for anything like this |
This should be fixed in the next Breathe release. |
Is your feature request related to a problem? Please describe.
I cannot combine MyST with other non-default Sphinx extensions, like breathe.
In RST, I would write::
.. doxygenstruct:: MyStruct
(https://breathe.readthedocs.io/en/latest/struct.html)
If I try
in MyST, it returns the following error:
Describe the solution you'd like
MyST should just let all directives through and pass handling of "unknown directive" to Sphinx itself.
Describe alternatives you've considered
Additional context
Tested with:
The text was updated successfully, but these errors were encountered: