markdown-link-check
markdown-link-check copied to clipboard
checks for anchor with consequent whitespaces fail in 3.12.2
Passes in 3.11.2 and fails in 3.12.2:
-
Whitespaces separated by special characters (no workaround)
[migrating from <= v1.18.0](#migrating-from--v1180) ### Migrating from `<= v1.18.0`Changing to
#migrating-from-v1180passes markdown-lint-check, but it breaks navigation in VSCode and other link checkers (e.g. table of content). -
Consequent whitespaces typo (easy to workaround)
[Client/server examples using `network.peer.*`](#clientserver-examples-using--networkpeer) ##### Client/server examples using `network.peer.*`
Could be related to similar issues: #348, #337
We use megalinter to run markdown-link-check on our PRs and our markdown files have TOCs generated via the markdown all in one vscode extension.
Having updated megalinter recently this bug has started to cause a lot of unnecessary noise about broken links that are not broken - with no sensible way of silencing them
This issue has been marked as stale because it has been open 60 days with no activity. It will be closed in 30 days unless the stale label is removed or someone adds a comment.
This was fixed by b2beaa0 (https://github.com/tcort/markdown-link-check/pull/328).
$ printf '[link to heading with special character](#has--special-character)\n\n## Has > Special Character\n\n[link to heading with consecutive spaces](#has--consecutive-spaces)\n\n## Has Consecutive Spaces' > /tmp/foo.md
$ npx github:tcort/markdown-link-check#3c31a25 /tmp/foo.md # Last bad commit.
FILE: C:/Users/per/AppData/Local/Temp/foo.md
[✖] #has--special-character
[✖] #has--consecutive-spaces
2 links checked.
ERROR: 2 dead links found!
[✖] #has--special-character → Status: 404
[✖] #has--consecutive-spaces → Status: 404
$ npx github:tcort/markdown-link-check#b2beaa0 /tmp/foo.md # First good commit.
FILE: C:/Users/per/AppData/Local/Temp/foo.md
[✓] #has--special-character
[✓] #has--consecutive-spaces
2 links checked.
This issue has been marked as stale because it has been open 60 days with no activity. It will be closed in 30 days unless the stale label is removed or someone adds a comment.
This issue was closed because it has been marked as stale for 90 days with no activity.