starred/markdownlint

Fork 0

mirror of https://github.com/DavidAnson/markdownlint.git synced 2026-04-25 09:16:02 +03:00

[GH-ISSUE #591] MD051/link-fragments false positive when code syntax is used #466

New issue

Closed

opened 2026-03-03 01:27:11 +03:00 by kerem · 6 comments

kerem commented

2026-03-03 01:27:11 +03:00

Owner

Originally created by @undergroundwires on GitHub (Oct 1, 2022).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/591

First of all thank you for the great tool. I use it on almost all of my projects. After upgrading to new version, I realized that MD051 fails to detect valid headers when code ``` backticks are used.

Example:


## `Header`

[Link](#Header) to header.

This is valid link and valid markdown but I get MD051/link-fragments Link fragments should be valid error.

Here is the markdown I use it on.

Originally created by @undergroundwires on GitHub (Oct 1, 2022). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/591 First of all thank you for the great tool. I use it on almost all of my projects. After upgrading to new version, I realized that MD051 fails to detect valid headers when code ``` backticks are used. Example: ```md ## `Header` [Link](#Header) to header. ``` This is valid link and valid markdown but I get `MD051/link-fragments Link fragments should be valid` error. Here is the [markdown](https://github.com/undergroundwires/privacy.sexy/blob/bd9f4bcaf8a4319473ae5ca2d25f0470276d23d8/docs/collection-files.md) I use it on.

kerem

2026-03-03 01:27:11 +03:00

closed this issue
added the
question
label

kerem commented

2026-03-03 01:27:12 +03:00

Author

Owner

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

It complains about the anchor not being lowercase, not the backticks

@nschonni commented on GitHub (Oct 1, 2022): It complains about the anchor not being lowercase, not the backticks

kerem commented

2026-03-03 01:27:12 +03:00

Author

Owner

@undergroundwires commented on GitHub (Oct 1, 2022):

Thank you for super fast response @nschonni , I'm too stupid, sorry for taking your time.

@undergroundwires commented on GitHub (Oct 1, 2022): Thank you for super fast response @nschonni , I'm too stupid, sorry for taking your time.

kerem commented

2026-03-03 01:27:12 +03:00

Author

Owner

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

No worries, it's one I hit before too. Not sure if the messaging needs to be updated

@nschonni commented on GitHub (Oct 1, 2022): No worries, it's one I hit before too. Not sure if the messaging needs to be updated

kerem commented

2026-03-03 01:27:12 +03:00

Author

Owner

@DavidAnson commented on GitHub (Oct 1, 2022):

I made myself a note to look into that.

@DavidAnson commented on GitHub (Oct 1, 2022): I made myself a note to look into that.

kerem commented

2026-03-03 01:27:12 +03:00

Author

Owner

@MFTabriz commented on GitHub (Oct 11, 2022):

Does the anchor really need to be in lowercase? RfC 3986 does not define the URI fragment as case in-sensitive (so it does not require normalization).

PS: I guess it must be due to the way it's been implemented in GH!

@MFTabriz commented on GitHub (Oct 11, 2022): Does the anchor really need to be in lowercase? RfC 3986 does not define the URI fragment as case in-sensitive (so it does not require normalization). PS: I guess it must be due to the way it's been implemented in GH!

kerem commented

2026-03-03 01:27:12 +03:00

Author

Owner

@DavidAnson commented on GitHub (Oct 11, 2022):

That's correct, GitHub appears to always use lowercase, and so that is the form this rule requires.

@DavidAnson commented on GitHub (Oct 11, 2022): That's correct, GitHub appears to always use lowercase, and so that is the form this rule requires.

kerem referenced this issue

2026-03-07 20:05:48 +03:00

[GH-ISSUE #466] Support for global config in home directory? #2231