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
It would be helpful when converting to other output formats if the parser added information to the AST to differentiate between an indented codeblock and a fenced codeblock. The use of these two forms often imply a different meaning (esp when both occur in the same document). At the moment, these two block types are indistinguishable in the AST.
I'm proposing a hint such as fenced: true in the options map for the parsed element (in the parse_codeblock_fenced method)
I'd be happy to provide a PR if this idea receives approval.
The text was updated successfully, but these errors were encountered:
It would be helpful when converting to other output formats if the parser added information to the AST to differentiate between an indented codeblock and a fenced codeblock. The use of these two forms often imply a different meaning (esp when both occur in the same document). At the moment, these two block types are indistinguishable in the AST.
I'm proposing a hint such as
fenced: true
in the options map for the parsed element (in the parse_codeblock_fenced method)I'd be happy to provide a PR if this idea receives approval.
The text was updated successfully, but these errors were encountered: