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
Describe the feature
Currently renderer methods get arguments cooked by marked Renderer Parser, as in code(code, infostring, escaped).
On the other hand, extensions rendered methods get a token parameter with all its properties.
I request that all renderer methods get a token.
Why is this feature necessary?
For example this.renderer.list won't know if the list is loose.
Describe alternatives you've considered
I could have asked for this.renderer.list to get a (body, ordered, start, loose) signature.
But passing the token around systematically seems to be much simpler.
The text was updated successfully, but these errors were encountered:
I would love this. It would make certain things so much easier. Unfortunately this would be a huge breaking change to most marked renderers. If we could do this in a way that would allow the tokens and deprecate the old way first I would be on board.
Describe the feature
Currently renderer methods get arguments cooked by marked
RendererParser, as incode(code, infostring, escaped)
.On the other hand, extensions rendered methods get a
token
parameter with all its properties.I request that all renderer methods get a token.
Why is this feature necessary?
For example this.renderer.list won't know if the list is loose.
Describe alternatives you've considered
I could have asked for this.renderer.list to get a
(body, ordered, start, loose)
signature.But passing the token around systematically seems to be much simpler.
The text was updated successfully, but these errors were encountered: