[GH-ISSUE #484] MD035 should ignore the leading > when checking a pattern #398

Closed
opened 2026-03-03 01:26:34 +03:00 by kerem · 3 comments
Owner

Originally created by @nschonni on GitHub (Jan 18, 2022).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/484

When checking a document for a HR of --- using

  "MD035": {
    "style": "---"
  },

on the following

> **Note:** _Remove this whole explanatory note before publishing_
>
> ---
>
> **Page front matter:**
>
> The frontmatter at the top of the page is used to define "page metadata".
> The values should be updated appropriately for the constructor.

It flags the > --- instead of ignoring the leading > because it is in a blockquote

[Expected: ---; Actual: > ---]

Originally created by @nschonni on GitHub (Jan 18, 2022). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/484 When checking a document for a HR of `---` using ```json "MD035": { "style": "---" }, ``` on the following ```md > **Note:** _Remove this whole explanatory note before publishing_ > > --- > > **Page front matter:** > > The frontmatter at the top of the page is used to define "page metadata". > The values should be updated appropriately for the constructor. ``` It flags the `> ---` instead of ignoring the leading `> ` because it is in a blockquote `[Expected: ---; Actual: > ---]`
kerem 2026-03-03 01:26:34 +03:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@DavidAnson commented on GitHub (Jan 18, 2022):

I think this is fixed in the latest version of the library for #430: https://dlaa.me/markdownlint/#%25m%23%20Issue%20484%0A%0AText%0A%0A---%0A%0A%3E%20Text%0A%3E%0A%3E%20---%0A%3E%0A%3E%20Text%0A

<!-- gh-comment-id:1015791710 --> @DavidAnson commented on GitHub (Jan 18, 2022): I think this is fixed in the latest version of the library for #430: https://dlaa.me/markdownlint/#%25m%23%20Issue%20484%0A%0AText%0A%0A---%0A%0A%3E%20Text%0A%3E%0A%3E%20---%0A%3E%0A%3E%20Text%0A
Author
Owner

@nschonni commented on GitHub (Jan 18, 2022):

OK, feel free to close. The only part I'm not sure the live site can test is if it was an issue with the explicit config causing the issue vs. the default "consistent"

<!-- gh-comment-id:1015794656 --> @nschonni commented on GitHub (Jan 18, 2022): OK, feel free to close. The only part I'm not sure the live site can test is if it was an issue with the explicit config causing the issue vs. the default "consistent"
Author
Owner

@DavidAnson commented on GitHub (Jan 18, 2022):

It should not matter, but you can include explicit config on the demo site with markdownlint-configure-file if you want to be sure.

<!-- gh-comment-id:1015805752 --> @DavidAnson commented on GitHub (Jan 18, 2022): It should not matter, but you can include explicit config on the demo site with markdownlint-configure-file if you want to be sure.
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#398
No description provided.