[GH-ISSUE #152] Fenced code blocks not recognized when nested under list item #1979

New issue

Closed

opened 2026-03-07 20:03:20 +03:00 by kerem · 2 comments

kerem commented

2026-03-07 20:03:20 +03:00

Owner

Originally created by @dbader on GitHub (Oct 31, 2018).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/152

Thanks for this awesome project, it's been incredibly helpful in standardizing the format of our written content 😄

I'm having an issue with fenced code blocks that are nested under list items not being recognized as code blocks. For example, the following file will trigger the no-multiple-blanks while inside the second code block.

test.md:

# Test

```text
line1


line2
```

- List item 1

    ```text
    line1


    line2
    ```

$ markdownlint test.md
test.md: 15: MD012/no-multiple-blanks Multiple consecutive blank lines [Expected: 1; Actual: 2]

Running markdownlint@0.11.0 via markdownlint-cli@0.13.0

Originally created by @dbader on GitHub (Oct 31, 2018). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/152 Thanks for this awesome project, it's been incredibly helpful in standardizing the format of our written content 😄 I'm having an issue with fenced code blocks that are nested under list items not being recognized as code blocks. For example, the following file will trigger the `no-multiple-blanks` while inside the second code block. `test.md`: # Test ```text line1 line2 ``` - List item 1 ```text line1 line2 ``` ```sh $ markdownlint test.md test.md: 15: MD012/no-multiple-blanks Multiple consecutive blank lines [Expected: 1; Actual: 2] ``` Running `markdownlint@0.11.0` via `markdownlint-cli@0.13.0`

kerem

2026-03-07 20:03:20 +03:00

closed this issue
added the
bug

fixed in next
labels

kerem commented

2026-03-07 20:03:22 +03:00

Author

Owner

@DavidAnson commented on GitHub (Oct 31, 2018):

Sorry about that, I think this is a duplicate of what’s underlying #151. I will look into this once I finish a couple of other in-progress projects. Thanks!

@DavidAnson commented on GitHub (Oct 31, 2018): Sorry about that, I think this is a duplicate of what’s underlying #151. I will look into this once I finish a couple of other in-progress projects. Thanks!

kerem commented

2026-03-07 20:03:22 +03:00

Author

Owner

@dbader commented on GitHub (Oct 31, 2018):

No worries at all David and THANKS SO MUCH for this awesome project, it's been incredibly helpful :)

@dbader commented on GitHub (Oct 31, 2018): No worries at all David and THANKS SO MUCH for this awesome project, it's been incredibly helpful :)

kerem referenced this issue

2026-03-07 20:09:36 +03:00

[GH-ISSUE #1979] Expose fix mode to custom rules (params.fixMode) #2643