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
Is your feature request related to a problem? Please describe.
The renderingConfig: { markedOptions: } option doesn't allow extensions to be passed to marked.
It appears that using the marked.use() function directly is the only way to add extensions without the complexity of creating another marked instance and providing that as a preview rendering function.
Describe the solution you'd like
An accessor function such as easyMDE.getMarked() would be ideal.
Describe alternatives you've considered
Passing a separate instance of marked in, but this increases the code size and seems needlessly complicated.
The text was updated successfully, but these errors were encountered:
I understand the desire to access easyMDE's internals and not to duplicate the marked package. However just like accessing the CodeMirror object (#76), I cannot guarantee that the entire marked package is included if at some future point the bundle is optimised with tree-shaking.
Extending renderingConfig with a markedExtensions option may be a better solution.
Is your feature request related to a problem? Please describe.
The renderingConfig: { markedOptions: } option doesn't allow extensions to be passed to marked.
It appears that using the marked.use() function directly is the only way to add extensions without the complexity of creating another marked instance and providing that as a preview rendering function.
Describe the solution you'd like
An accessor function such as easyMDE.getMarked() would be ideal.
Describe alternatives you've considered
Passing a separate instance of marked in, but this increases the code size and seems needlessly complicated.
The text was updated successfully, but these errors were encountered: