[GH-ISSUE #605] MD051 option lowerCase #2323

Closed
opened 2026-03-07 20:06:42 +03:00 by kerem · 3 comments
Owner

Originally created by @nschonni on GitHub (Oct 12, 2022).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/605

Since this has come up in a few separate issues, I thought I'd write down a proposal.

# Title

[Good, "lowerCase": true](#title)

[Good, "lowerCase": false](#Title)

An alternate take to this, would be to have the rule fix the anchor if it matches, but the case doesn't

Originally created by @nschonni on GitHub (Oct 12, 2022). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/605 Since this has come up in a few separate issues, I thought I'd write down a proposal. ```md # Title [Good, "lowerCase": true](#title) [Good, "lowerCase": false](#Title) ``` An alternate take to this, would be to have the rule fix the anchor if it matches, but the case doesn't
kerem 2026-03-07 20:06:42 +03:00
Author
Owner

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

There may be another way to name the option, like anyCase, which would still likely just lower it for comparison.

<!-- gh-comment-id:1281812744 --> @nschonni commented on GitHub (Oct 18, 2022): There may be another way to name the option, like `anyCase`, which would still likely just lower it for comparison.
Author
Owner

@DavidAnson commented on GitHub (Dec 8, 2022):

I don't think it's necessary to add an option here since the rule currently implements the GitHub algorithm which uses lowercase all the time. However, the suggestion to provide a fix for cases where an existing label with different case is present seems good.

<!-- gh-comment-id:1341885110 --> @DavidAnson commented on GitHub (Dec 8, 2022): I don't think it's necessary to add an option here since the rule currently implements the GitHub algorithm which uses lowercase all the time. However, the suggestion to provide a fix for cases where an existing label with different case is present seems good.
Author
Owner

@nschonni commented on GitHub (Dec 8, 2022):

If there is no extra option, there may just need to be a separate error message so those folks that ran into the casing issue but see that existing one works, understand the failure better

<!-- gh-comment-id:1341902910 --> @nschonni commented on GitHub (Dec 8, 2022): If there is no extra option, there may just need to be a separate error message so those folks that ran into the casing issue but see that existing one works, understand the failure better
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#2323
No description provided.