mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-25 09:16:02 +03:00
[GH-ISSUE #548] MD051 false error #2297
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#2297
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 @viceice on GitHub (Aug 4, 2022).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/548
Consider this:
That causes the following error
It seems the space encoding isn't accepted. Happens since
markdownlint-cli2v0.5.0github.com/renovatebot/renovate@e02967e3cd/docs/usage/nuget.md (L29)@nschonni commented on GitHub (Aug 4, 2022):
An anchor link points to an ID, which can't contain a space https://html.spec.whatwg.org/multipage/dom.html#the-id-attribute
@viceice commented on GitHub (Aug 4, 2022):
ok, but how do we address that headline?
@DavidAnson commented on GitHub (Aug 4, 2022):
The example above is not canonical on GitHub because GitHub represents the heading like this: #alternate-feeds. (Specifically https://github.com/renovatebot/renovate/blob/e02967e3cda1f9e6c5452b032822fe532cdb5ac7/docs/usage/nuget.md#alternate-feeds if you click on the anchor.) This linking behavior is not part of the CommonMark standard, but this rule enforces GitHub syntax and therefore the violation is intended. That said, the link you provide does work in that document and I think perhaps GitHub is handling the mismatch (can't check from my phone). But I think it is reasonable for the rule to complain here since the link does not match what the document produces.
@DavidAnson commented on GitHub (Oct 18, 2022):
Closing in favor of #605.