fix: don't de-indent HTML inside fenced code blocks - #130
Open
reidransom wants to merge 1 commit into
Open
Conversation
deIndentHTMLBlocks operates on raw markdown lines before Goldmark parses them, so a line like <ul> inside a ``` fence started an "HTML block" and the following indented code-sample lines lost their leading spaces in the rendered <pre> output. Track fence state (``` and ~~~) and leave fenced content untouched.
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
1 participant
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.
Hello- love this repo, I'm using it on all my websites. This is my first PR. Let me know if I can make any changes or missed any guidelines. Thank you!
deIndentHTMLBlocks operates on raw markdown lines before Goldmark parses them, so a line like
inside a ``` fence started an "HTML block" and the following indented code-sample lines lost their leading spaces in the rendered