New rule suggestion: detect link that point to nothing
See original GitHub issueExample:
[link][bad-link]
[good-link]: https://google.com
Currently this does not produce an error.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:11
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Evolving "nofollow" – new ways to identify the nature of links
Links contain valuable information that can help us improve search, such as how the words within links describe content they point at.
Read more >Understanding SC 2.4.4:Link Purpose (In Context) (Level A)
In this case the user should be able to identify the purpose of the link without moving focus from the link. In other...
Read more >Links - Usability & Web Accessibility - Yale University
As a general rule, link text alone should be enough to convey the purpose of the link. But, some visual designs do not...
Read more ><a>: The Anchor element - HTML: HyperText Markup Language
External links and linking to non-HTML resources. Links that open in a new tab/window via target="_blank" , or links that point to a...
Read more >Instagram Bio Link Not Working? New Solutions for 2022
Select Broadband (Ethernet) under Rule Name. Go to Settings. Click on Renew > Release > Apply. Now check if Instagram Link not allowed...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This should be broken into a couple of separate rules:
[bad-link]
), which is unambiguously bad[good-link]
), which can be harmless@lorenzleutgeb This seems reasonable to do as two different rules. You might also see if this behavior makes sense to fold into one of them: https://github.com/DavidAnson/markdownlint/issues/213. (I checked the other link-related issues and they do not seem relevant.) If you’d like early and regular feedback, I’m happy to look over draft PR’s as you make progress. Thanks!