[GH-ISSUE #177] MD025 conflicts with hexo #153

Closed
opened 2026-03-03 01:24:11 +03:00 by kerem · 2 comments
Owner

Originally created by @MisakaMikoto19090 on GitHub (Apr 11, 2019).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/177

MD025 used to work fine with my hexo blogs. today there is a warning .

Is this a bug? Or is there a way to disable MD025.

Annotation 2019-04-11 111844

Originally created by @MisakaMikoto19090 on GitHub (Apr 11, 2019). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/177 MD025 used to work fine with my hexo blogs. today there is a warning . Is this a bug? Or is there a way to disable MD025. ![Annotation 2019-04-11 111844](https://user-images.githubusercontent.com/10293827/55928647-1c163c80-5c4c-11e9-9e97-0bed3bc53c1d.png)
kerem 2026-03-03 01:24:11 +03:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@DavidAnson commented on GitHub (Apr 11, 2019):

This seems like a bug fix. :) MD025 reports a violation when there are multiple top level headings (usually h1) in a document. You have one of those on line 13. What’s new is that “title“ properties in YAML front matter are also treated like a top level heading because most blog engines use those as the title. You can disable the new behavior by customizing the rule. This is discussed more in the documentation: https://github.com/DavidAnson/markdownlint/blob/master/doc/Rules.md#

Hope this helps!

<!-- gh-comment-id:481952976 --> @DavidAnson commented on GitHub (Apr 11, 2019): This seems like a bug fix. :) MD025 reports a violation when there are multiple top level headings (usually h1) in a document. You have one of those on line 13. What’s new is that “title“ properties in YAML front matter are also treated like a top level heading because most blog engines use those as the title. You can disable the new behavior by customizing the rule. This is discussed more in the documentation: https://github.com/DavidAnson/markdownlint/blob/master/doc/Rules.md# Hope this helps!
Author
Owner

@MisakaMikoto19090 commented on GitHub (Apr 11, 2019):

thank you very much for your time.I should have double check the doc first.

<!-- gh-comment-id:481958591 --> @MisakaMikoto19090 commented on GitHub (Apr 11, 2019): thank you very much for your time.I should have double check the doc first.
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#153
No description provided.