Skip to content

🐛 [md] Sub ordered list with post list marker space #10374

@ematipico

Description

@ematipico

Environment information

main

What happened?

The current markdown, generate incorrect CST

1.  123
2.  123
    1.   123
    2.   123

Generates

0: [email protected]
  0: (empty)
  1: [email protected]
    0: [email protected]
      0: [email protected]
        0: [email protected]
          0: [email protected]
            0: [email protected]
            1: [email protected] "1." [] []
            2: [email protected] "  " [] []
            3: [email protected]
          1: [email protected]
            0: [email protected]
              0: [email protected]
                0: [email protected]
                  0: [email protected] "first" [] []
                1: [email protected]
                  0: [email protected] "\n" [] []
              1: (empty)
        1: [email protected]
          0: [email protected]
            0: [email protected]
            1: [email protected] "2." [] []
            2: [email protected] "  " [] []
            3: [email protected]
          1: [email protected]
            0: [email protected]
              0: [email protected]
                0: [email protected]
                  0: [email protected] "second" [] []
                1: [email protected]
                  0: [email protected] "\n" [] []
              1: (empty)
            1: [email protected]
              0: [email protected]
                0: [email protected]
                  0: [email protected] " " [] []
                1: [email protected]
                  0: [email protected] " " [] []
                2: [email protected]
                  0: [email protected] " " [] []
                3: [email protected]
                  0: [email protected] " " [] []
            2: [email protected]
              0: [email protected]
                0: [email protected]
                  0: [email protected]
                    0: [email protected]
                    1: [email protected] "1." [] []
                    2: [email protected] "   " [] []
                    3: [email protected]
                  1: [email protected]
                    0: [email protected]
                      0: [email protected]
                        0: [email protected]
                          0: [email protected] "third" [] []
                        1: [email protected]
                          0: [email protected] "\n" [] []
                        2: [email protected]
                          0: [email protected] " " [] []
                        3: [email protected]
                          0: [email protected] " " [] []
                        4: [email protected]
                          0: [email protected] " " [] []
                        5: [email protected]
                          0: [email protected] " " [] []
                        6: [email protected]
                          0: [email protected] "2." [] []
                        7: [email protected]
                          0: [email protected] "   fourth" [] []
                        8: [email protected]
                          0: [email protected] "\n" [] []
                      1: (empty)
  2: [email protected] "" [] []

Everything after the second 1. is parsed text, breaking common mark.

Source

---
1. 123
2. 123
1. 123
2. 123
---
1. 123
2. 123
1. 123
2. 123

Expected result

It should be parsed as two sub MdBullet

https://spec.commonmark.org/dingus/?text=1.%20%20123%0A2.%20%20123%0A%20%20%20%201.%20%20%20123%0A%20%20%20%202.%20%20%20123

The bug is subtle because it doesn't happen with

1. 123
2. 123
   1.   123
   2.   123

cc @jfmcdowell

Code of Conduct

  • I agree to follow Biome's Code of Conduct

Metadata

Metadata

Assignees

Labels

A-ParserArea: parserL-MarkdownLanguage: MarkdownS-Bug-confirmedStatus: report has been confirmed as a valid bug

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions