Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Ordered lists split up after 10th item #43

Closed
4 tasks done
brianzaubar opened this issue Apr 4, 2025 · 7 comments
Closed
4 tasks done

Ordered lists split up after 10th item #43

brianzaubar opened this issue Apr 4, 2025 · 7 comments
Labels
🙋 no/question This does not need any changes 👎 phase/no Post cannot or will not be acted on

Comments

@brianzaubar
Copy link

Initial checklist

Affected package

2.0.2

Steps to reproduce

We are running a web-server with nuxt.js and vue.js.
My example list:

1. **Header 1**
   - header 1 item 1
   - header 1 item 2
2. **Header 2**
   - header 2 item 1
   - header 2 item 2
3. **Header 3**
   - header 3 item 1
   - header 3 item 2
4. **Header 4**
   - header 4 item 1
   - header 4 item 2
5. **Header 5**
   - header 5 item 1
   - header 5 item 2
6. **Header 6**
   - header 6 item 1
   - header 6 item 2
7. **Header 7**
   - header 7 item 1
   - header 7 item 2
8. **Header 8**
   - header 8 item 1
   - header 8 item 2
9. **Header 9**
   - header 9 item 1
   - header 9 item 2
10. **Header 10**
   - header 10 item 1
   - header 10 item 2
11. **Header 11**
   - header 11 item 1
   - header 11 item 2

Actual behavior

Ordered lists always break up after the 10th items. Meaning the ast tree will have several items of type "list" as siblings even though they belong to one list.
Here you can see too many entries:

Image

Expected behavior

This behaviour does not happen in unordered lists. I expect the ordered list to be one item and not several after the 10th item.

Runtime

node@20.16.0, Chrome 134.0.6998.166

Package manager

bun@1.1.29, npm@10.8.1

Operating system

macOS Sequoia 15.3.2

Build and bundle tools

other (please specify in steps to reproduce)

@github-actions github-actions bot added 👋 phase/new Post is being triaged automatically 🤞 phase/open Post is being triaged manually and removed 👋 phase/new Post is being triaged automatically labels Apr 4, 2025
@remcohaszing
Copy link
Member

This is expected behaviour. It happens on GitHub too.

  1. Header 1
    • header 1 item 1
    • header 1 item 2
  2. Header 2
    • header 2 item 1
    • header 2 item 2
  3. Header 3
    • header 3 item 1
    • header 3 item 2
  4. Header 4
    • header 4 item 1
    • header 4 item 2
  5. Header 5
    • header 5 item 1
    • header 5 item 2
  6. Header 6
    • header 6 item 1
    • header 6 item 2
  7. Header 7
    • header 7 item 1
    • header 7 item 2
  8. Header 8
    • header 8 item 1
    • header 8 item 2
  9. Header 9
    • header 9 item 1
    • header 9 item 2
  10. Header 10
  • header 10 item 1
  • header 10 item 2
  1. Header 11
  • header 11 item 1
  • header 11 item 2

You need to properly indent list items:

1. **Header 1**
   - header 1 item 1
   - header 1 item 2
2. **Header 2**
   - header 2 item 1
   - header 2 item 2
3. **Header 3**
   - header 3 item 1
   - header 3 item 2
4. **Header 4**
   - header 4 item 1
   - header 4 item 2
5. **Header 5**
   - header 5 item 1
   - header 5 item 2
6. **Header 6**
   - header 6 item 1
   - header 6 item 2
7. **Header 7**
   - header 7 item 1
   - header 7 item 2
8. **Header 8**
   - header 8 item 1
   - header 8 item 2
9. **Header 9**
   - header 9 item 1
   - header 9 item 2
10. **Header 10**
    - header 10 item 1
    - header 10 item 2
11. **Header 11**
    - header 11 item 1
    - header 11 item 2
  1. Header 1
    • header 1 item 1
    • header 1 item 2
  2. Header 2
    • header 2 item 1
    • header 2 item 2
  3. Header 3
    • header 3 item 1
    • header 3 item 2
  4. Header 4
    • header 4 item 1
    • header 4 item 2
  5. Header 5
    • header 5 item 1
    • header 5 item 2
  6. Header 6
    • header 6 item 1
    • header 6 item 2
  7. Header 7
    • header 7 item 1
    • header 7 item 2
  8. Header 8
    • header 8 item 1
    • header 8 item 2
  9. Header 9
    • header 9 item 1
    • header 9 item 2
  10. Header 10
    • header 10 item 1
    • header 10 item 2
  11. Header 11
    • header 11 item 1
    • header 11 item 2

@remcohaszing remcohaszing closed this as not planned Won't fix, can't repro, duplicate, stale Apr 4, 2025

This comment has been minimized.

@remcohaszing remcohaszing added 🙋 no/question This does not need any changes 👎 phase/no Post cannot or will not be acted on and removed 🤞 phase/open Post is being triaged manually labels Apr 4, 2025
Copy link

github-actions bot commented Apr 4, 2025

Hi! Thanks for reaching out! Because we treat issues as our backlog, we close issues that are questions since they don’t represent a task to be completed.

See our support docs for how and where to ask questions.

Thanks,
— bb

@brianzaubar
Copy link
Author

Ah alright. Okay thanks. Interesting behaviour.

@liangxiwei
Copy link

liangxiwei commented Apr 9, 2025

you know, some markdown text is generated by AI. And the markdown is not always standard. If we do not adapt it, it will alway has bug.

@JounQin
Copy link
Member

JounQin commented Apr 9, 2025

It's AI's bug, not here. Markdown has a standard spec: commonmark.

@ChristianMurphy
Copy link
Member

Markdown has a standard.

Train your AI.

Use LLM guidance like https://github.com/guidance-ai/guidance, https://github.com/outlines-dev/outlines, https://github.com/stanfordnlp/dspy, https://github.com/eth-sri/lmql, https://github.com/instructor-ai/instructor, and many others. Which can ensure the model generates valid markdown.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
🙋 no/question This does not need any changes 👎 phase/no Post cannot or will not be acted on
Development

No branches or pull requests

5 participants