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
This is an interesting project! I found my way here after bumping into pragdave/earmark#228 (earmark does not parse content inside of html tags as markdown) which led me to trying the Cmark parser bundled with ExDoc. This produced much better results (formatted markdown inside html tags) except the syntax highlighting for elixir code was gone. A few steps later and here I am.
This library depends on Earmark explicitly. Both this library and the Cmark processor need to be specified as the markdown_processor to ExDoc.
Is it possible for ex_doc_makeup to support a configurable parser?
EDIT:
Digging in further I'm guessing the main reason this would be difficult or impossible is that Cmark doesn't provide a callback for each block (or a configurable code renderer of any sort) since it's shelling out to a C library under the hood.
Feel free to close if this is a no-go. :)
The text was updated successfully, but these errors were encountered:
This is an interesting project! I found my way here after bumping into pragdave/earmark#228 (
earmark
does not parse content inside of html tags as markdown) which led me to trying the Cmark parser bundled with ExDoc. This produced much better results (formatted markdown inside html tags) except the syntax highlighting for elixir code was gone. A few steps later and here I am.This library depends on Earmark explicitly. Both this library and the Cmark processor need to be specified as the
markdown_processor
to ExDoc.Is it possible for
ex_doc_makeup
to support a configurable parser?EDIT:
Digging in further I'm guessing the main reason this would be difficult or impossible is that Cmark doesn't provide a callback for each block (or a configurable code renderer of any sort) since it's shelling out to a C library under the hood.
Feel free to close if this is a no-go. :)
The text was updated successfully, but these errors were encountered: