Repository navigation
Keep paragraph tags paired in multi-block Markdown list items - #157
Merged
Merged
Conversation
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
2 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.
A list item containing a paragraph, a code block (or quote/nested list), and another paragraph produces unmatched paragraph tags. For example,
- Introductionfollowed by an indented code block andConclusioncurrently renders the item asIntroduction</p>...<p>Conclusion: the outer-wrapper regex removes tags belonging to two different paragraphs.Only unwrap a rendered list body when it consists of one paragraph. Keep the complete block structure for multi-block items, while preserving compact single-line and plain continuation items.
Validation: the unchanged upstream fails three new regressions and passes two controls. All five new tests pass after the fix, along with the parser-progress regression and six existing list/fence checks (12 total). TypeScript build/no-emit checks and Prettier checks pass. Tests cover intervening code, a blockquote, a nested list, ordinary continuation text, and a final code block.
Submitted under the published $0.25 USD-equivalent reward per valid bug-fix PR, using the existing application and settlement conversation. Settlement remains native SOL on Solana mainnet, subject to acceptance and confirmation of the exact token amount. No reward is claimed as received.