MD035: Horizontal Rule enforcement broken
See original GitHub issueDependency versions:
- markdownlint-cli:
0.31.1
- markdownlint:
0.25.1
- markdown-it:
12.3.2
- markdown-it:
- markdownlint:
Rule
# MD035 - Horizontal rule style
hr-style:
style: "* * *"
Description
Previously (0.24.0) using - - -
would throw this error:
[Expected: * * *; Actual: - - -]
Now it throws:
[Expected: * * *; Actual: ---]
Same with * * * *
- Before:
[Expected: * * *; Actual: * * * *]
- Now:
[Expected: * * *; Actual: ****]
Reproduction
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
markdownlint/Rules.md at main - GitHub
A line of text followed by a horizontal rule becomes a heading --- ... The default value allows 2 spaces to indicate a...
Read more ><hr>: The Thematic Break (Horizontal Rule) element - HTML
The HTML element represents a thematic break between paragraph-level elements: for example, a change of scene in a story, or a shift of ......
Read more >Markdown Style Guide - Rocket.Chat Docs
MD035 - Horizontal rule style ... Horizontal rules should be created using three slashes ( --- ).
Read more >Horizontal Rule Broken? - Resolved help - Obsidian Forum
When I try to create a horizontal rule with 3 dashes, it doesn't create a line in preview mode. If I create it...
Read more >Not Your Typical Horizontal Rules - Sara Soueidan
A horizontal rule is used to provide a visual break and divide content. Like other HTML elements, horizontal rules can be styled using...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Fair points. I have an idea how to be picky in the current context and will explore that when I get to this issue. It sounds like you want the freedom to define a break as “* * *” and have that exclusively enforced.
Unrelated, I don’t think it’s fair to blame
markdown-it
for any problems related to this project. I’m (ab)using it for a purpose it wasn’t intended to support. 😃Ugh, I “improved” this rule by relying more on the parser to identify syntax, but it seems to be normalizing and that leads to this problem.