mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-25 01:05:55 +03:00
[GH-ISSUE #81] Rule request: one sentence per line #66
Labels
No labels
bug
enhancement
enhancement
enhancement
fixed in next
fixed in next
fixed in next
new rule
new rule
new rule
pull-request
question
refactoring
refactoring
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/markdownlint#66
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JoshuaKGoldberg on GitHub (Oct 22, 2017).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/81
A lot of markdown commits are small corrections such as spelling or grammar fixes. Having multiple sentences in a line increases the git commit diff size for these smaller fixes. It's good to follow all sentence-ending periods with an endline to reduce the chance of conflicts.
For documentation that tends towards long sentences, this can be a good alternative to strict line lengths.
@DavidAnson commented on GitHub (Oct 22, 2017):
Great idea! This is a pattern I try to follow myself.
@KvanTTT commented on GitHub (Oct 28, 2017):
Also, I suggest an 80-line string length pattern (80 can be changed to another custom value).
@DavidAnson commented on GitHub (Oct 28, 2017):
@KvanTTT That exists: https://github.com/DavidAnson/markdownlint/blob/master/doc/Rules.md#md013
@KvanTTT commented on GitHub (Oct 28, 2017):
Cool! This was not working for me: disabled in VSCode extension by default :)
@DavidAnson commented on GitHub (Dec 18, 2017):
Closing as duplicate of #66.