Repository navigation
fix: markdown — an indented fence inside a code block does not close it - #59
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Found on a real README (embed's): an
html block holding an HTML example with a `<script type="text/markdown">` inside, whosemermaid lines are indented. The renderer took the inner, indented ``` for the end of the outer block: the rest of the README rendered as a code block and its tables as text.A closing fence now has to be the same character, at least as long, nothing after it, and indented at most three spaces more than the opening fence (CommonMark's rule, relative to the opening so fenced blocks inside list items still close). Same in
splitMarkdown.Test added; 1262 tests pass.
🤖 Generated with Claude Code