fix: indent loose list continuation content under parent bullet#705
Merged
Conversation
The markdown parser now merges blank-line-separated indented content into the preceding list item (loose continuation), matching standard markdown behavior. The renderer splits multi-paragraph list items on double newlines and renders each as a separate <p> under the bullet. Closes #704
The previous commit tightened the indent regex from \s+ to \s{2,} for
both tight and loose cases, breaking single-space and tab tight
continuations. Now tight uses \s+ (original) and only loose requires
\s{2,}.
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.
Summary
\n\nand renders each segment as a separate<p>under the bullet, keeping content visually indented\s+indent check; only loose continuation (after blank line) requires\s{2,}Closes #704
Test plan
./tests/manual/local/test-loose-list.shand walk through all 16 sections of the fixture — each section describes expected rendering and what a regression looks likebun test packages/ui/utils/parser.test.ts— all 103 tests pass