[GH-ISSUE #1532] Is the MD029/ol-prefix rule being triggered incorrectly? #2548

Closed
opened 2026-03-07 20:08:48 +03:00 by kerem · 2 comments
Owner

Originally created by @clicktodev on GitHub (Mar 7, 2025).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/1532

what's wrong with this?

Image

Local Development Setup

  1. Clone the repository
git clone https://github.com/hichemfantar/freedraw.git
cd freedraw
  1. Install dependencies
npm install
# or
yarn install
# or
pnpm install
Originally created by @clicktodev on GitHub (Mar 7, 2025). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/1532 what's wrong with this? ![Image](https://github.com/user-attachments/assets/1ac8053e-9795-4c48-8fd1-f4d8d602ce29) ### Local Development Setup 1. **Clone the repository** ```bash git clone https://github.com/hichemfantar/freedraw.git cd freedraw ``` 2. **Install dependencies** ```bash npm install # or yarn install # or pnpm install ```
kerem 2026-03-07 20:08:48 +03:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@DavidAnson commented on GitHub (Mar 7, 2025):

Because the code fences are not indented, what you show above is three separate lists and the lint rule is correctly saying the second and third do not begin with the number 1. If your intent is for that to be a single list with three items, the code fences need to be indented to line up under the first character of the list content – three spaces for the example above.

<!-- gh-comment-id:2707683042 --> @DavidAnson commented on GitHub (Mar 7, 2025): Because the code fences are not indented, what you show above is three separate lists and the lint rule is correctly saying the second and third do not begin with the number 1. If your intent is for that to be a single list with three items, the code fences need to be indented to line up under the first character of the list content – three spaces for the example above.
Author
Owner

@clicktodev commented on GitHub (Mar 8, 2025):

I tried it at first but it turns out it needs to be indented at the same level as the bullet title. thanks!

<!-- gh-comment-id:2708340870 --> @clicktodev commented on GitHub (Mar 8, 2025): I tried it at first but it turns out it needs to be indented at the same level as the bullet title. thanks!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/markdownlint#2548
No description provided.