[GH-ISSUE #24] Request: No empty link rule #17

Closed
opened 2026-03-03 01:23:03 +03:00 by kerem · 2 comments
Owner

Originally created by @originalfoo on GitHub (Jun 22, 2016).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/24

When working on large documents, sometimes placeholder links are added with the expectation they will be defined later. For example:

[foo]()

[bar](#)

Such links are somewhat difficult to spot in big documents. The rule would warn against those patterns.

Note: A # link is sometimes used to jump to top of document, however similar effect can be achieved by linking to main heading or a html anchor tag.

Originally created by @originalfoo on GitHub (Jun 22, 2016). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/24 When working on large documents, sometimes placeholder links are added with the expectation they will be defined later. For example: ``` [foo]() [bar](#) ``` Such links are somewhat difficult to spot in big documents. The rule would warn against those patterns. Note: A `#` link is sometimes used to jump to top of document, however similar effect can be achieved by linking to main heading or a html anchor tag.
kerem 2026-03-03 01:23:03 +03:00
Author
Owner

@DavidAnson commented on GitHub (Jun 23, 2016):

A bit tangential, but this is starting to veer pretty close to an existing check-pages feature:
https://github.com/DavidAnson/check-pages#noemptyfragments

No objection to adding to markdownlint, however. :)

<!-- gh-comment-id:227952636 --> @DavidAnson commented on GitHub (Jun 23, 2016): A bit tangential, but this is starting to veer pretty close to an existing `check-pages` feature: https://github.com/DavidAnson/check-pages#noemptyfragments No objection to adding to `markdownlint`, however. :)
Author
Owner

@originalfoo commented on GitHub (Aug 22, 2016):

Been away due to RL issues, but great to see this feature implemented - many thanks!

<!-- gh-comment-id:241300835 --> @originalfoo commented on GitHub (Aug 22, 2016): Been away due to RL issues, but great to see this feature implemented - many thanks!
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#17
No description provided.