fix: treat unclosed markdown fences as extending to EOF - #29
Merged
royalpinto007 merged 1 commit intoSep 12, 2026
Merged
royalpinto007 merged 1 commit into
royalpinto007 merged 1 commit into
Conversation
When a fenced code block has no closing fence, codeBlockRanges now covers from the opening fence through end of file so prose rules stay out of code and code rules still apply. Fixes #12 Co-authored-by: Sharad. <sharadvc@users.noreply.github.com>
1 task
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
3 participants
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.
Summary
Unclosed fenced code blocks left
codeBlockRangesempty, so prose rules could match inside code and code rules did not run there. Opening fences without a closer now extend through EOF.Test plan
npm test— regression for unclosed fence prose/code boundariesFixes #12