[GH-ISSUE #228] All rules should include Rationale #197

Closed
opened 2026-03-03 01:24:36 +03:00 by kerem · 1 comment
Owner

Originally created by @displague on GitHub (Oct 14, 2019).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/228

The use of this linter in a project should not require a developer to use the existence of this linter as the primary support.

Some rules include rationale, while others do not. It would build the case for markdown lint adoption if all rules included well reasoned and supported rationale, including references to deeper discussions for each rule.

https://github.com/DavidAnson/markdownlint/blob/master/doc/Rules.md#md026---trailing-punctuation-in-heading is an example of a rule that offers no rationale.

Originally created by @displague on GitHub (Oct 14, 2019). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/228 The use of this linter in a project should not require a developer to use the existence of this linter as the primary support. Some rules include rationale, while others do not. It would build the case for markdown lint adoption if all rules included well reasoned and supported rationale, including references to deeper discussions for each rule. https://github.com/DavidAnson/markdownlint/blob/master/doc/Rules.md#md026---trailing-punctuation-in-heading is an example of a rule that offers no rationale.
kerem 2026-03-03 01:24:36 +03:00
Author
Owner

@displague commented on GitHub (Jan 28, 2020):

Thanks, @DavidAnson !

<!-- gh-comment-id:579237472 --> @displague commented on GitHub (Jan 28, 2020): Thanks, @DavidAnson !
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#197
No description provided.