mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-26 09:46:01 +03:00
[GH-ISSUE #126] Modify MD029 to allow 0 as an option #1954
Labels
No labels
bug
enhancement
enhancement
enhancement
fixed in next
fixed in next
fixed in next
new rule
new rule
new rule
pull-request
question
refactoring
refactoring
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/markdownlint#1954
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @marvhen on GitHub (Jun 7, 2018).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/126
Hi thanks for markdownlint...I really like it!
What do you think about modifying the MD029/ol-prefix: Ordered list item prefix rule (and/or MD005/list-indent) to allow numeric list markers to align vertically on their decimal position? This, in my opinion, improves readability when viewing the markdown as plain text.
Attached are some examples. I tried creating a custom rule by starting out with the built-in rule but I get I'm not sure how to include shared.js.
@DavidAnson commented on GitHub (Jun 7, 2018):
This seems reasonable and is allowed by the CommonMark specification. I'll give this a try in the next round of updates, thanks!
Regarding custom rules,
shared.jsis not required. You can see simple examples here: https://github.com/DavidAnson/markdownlint/blob/master/doc/CustomRules.md@marvhen commented on GitHub (Jun 7, 2018):
Thanks! awesome.
I'll look at the examples a little closer...for some reason I was thinking I needed to be able to call
flattenLists().@DavidAnson commented on GitHub (Jun 7, 2018):
flattenListsis convenient, but not necessary. Or you could duplicate it. Some of the helper methods were weird enough that I did not want to make them a supported public API.