fix(render): correct list indentation and block content in list items

[ManUtopiK]

Summary

Fix two markdown rendering bugs in renderMarkdown:

• renderMarkdown nested lists indentation is off inside ordered lists #114 — Nested list indentation: Nested lists now use the correct indentation width matching the parent list marker (3 spaces for 1. , 2 spaces for - ), conforming to CommonMark 0.31.2 §5.2 — continuation blocks must be indented to the column of the first non-blank character after the list marker (Examples 254, 109).
• renderMarkdown merges code blocks into preceding text inside list items #118 — Block content in list items: Block-level elements (pre, blockquote, table) inside list items are now rendered on their own line with proper indentation, instead of being concatenated to the preceding inline text. Per CommonMark 0.31.2 §5.2 Example 263, fenced code blocks in list items must be indented to align with list content.

Changes

File	Change
indent.ts	Add width parameter for character-count indentation
ul.ts	Set listIndent: 2 in context (matches - prefix)
ol.ts	Set listIndent: 3 in context (matches 1. prefix)
li.ts	Detect block-level children, render them on a new line with prefix-aligned indentation
3 SPEC files	Update expected markdown output to match corrected behavior

Test plan

• All existing tests pass (746 passed, 2 pre-existing shiki timeouts unrelated)
• Roundtrip stable: parse → renderMarkdown → parse → renderMarkdown produces identical output
• Verified against CommonMark spec §5.2: indentation matches the column of first content after list marker

Closes #114, closes #118

[vercel]

@ManUtopiK is attempting to deploy a commit to the NuxtLabs Team on Vercel.

A member of the Team first needs to authorize it.

[pkg-pr-new]

Open in StackBlitz

comark

npm i https://pkg.pr.new/comarkdown/comark@120

@comark/ansi

npm i https://pkg.pr.new/comarkdown/comark/@comark/ansi@120

@comark/html

npm i https://pkg.pr.new/comarkdown/comark/@comark/html@120

@comark/nuxt

npm i https://pkg.pr.new/comarkdown/comark/@comark/nuxt@120

@comark/react

npm i https://pkg.pr.new/comarkdown/comark/@comark/react@120

@comark/svelte

npm i https://pkg.pr.new/comarkdown/comark/@comark/svelte@120

@comark/vue

npm i https://pkg.pr.new/comarkdown/comark/@comark/vue@120

commit: 4a1f5c6

[farnabaz]

Are you sure that these replaces are needed?
I just checked and even with removing these replaces tests passed.

I didn't get the real reason behind these replaces, maybe these are useful when li have multiple chilred.

Could you add a test to check against these replaces? 🙏

[ManUtopiK]

You're right!
I tested with and without the .replace() and the output is the same in all cases. I started this current fix for some experiments with markdownlint. I didn't remember why I added this lines... so I removed them.

To be sure, I also added 7 SPEC tests to cover all cases (blockquote, table, code blocks, nested ol/ul up to 3 levels) here : ManUtopiK@f4c2330

Should I merge these tests ? Is it too much ? Or in another PR ?

[farnabaz]

It's never too much to have more tests 🙂
Feel free to push it in this PR 👍

[ManUtopiK]

C'est fait !

[farnabaz]

Thanks for the PR @ManUtopiK
I just add a comment on the li handler, other than that it looks great 🙂

[farnabaz]

Thanks