Add default renderers for html nodes pointing at the README - #70
Merged
Conversation
Contributor
Author
Collaborator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses #69.
Parsing was already CommonMark compliant.
<del>\n\n*foo*\n\n</del>(https://spec.commonmark.org/0.30/#example-167) parses to html-block, paragraph, html-block, and the<aside>case in the issue matches what markdown-it produces. What made HTML look broken is thatdefault-hiccup-renderershad no entry for:html-blockand:html-inline, so->hiccupfell through to the generic "Unknown type" span.:html-blockand:html-inlinethat say there is no default renderer and link to the README section.:htmltypo, and document that an HTML block ends at the first blank line.html_inline/html_blockdefmethods inimpl.cljs.Rendering raw HTML by default is still not the behaviour, since that means unescaped passthrough.