Feature suggestion: Automating wrapping markdown one-sentence-per-line

[dstansby]

Is Your Feature Request Related to a Problem? Please Describe

Add an automated way to wrap markdown files at 80 (@dstansby: maybe a bit more??) characters.

Suggested by @paddyroddy in #335 (comment).

Describe the Solution You'd Like

An automated way to wrap markdown files in the pre-commit config.

Describe Alternatives You've Considered

No response

Additional Context

No response

[paddyroddy]

Identified in #361 proseWrap broke things due to prettier/prettier#9232. This might be fixable by a different markdown parser, or not using the RST-like hyperlink format.

[matt-graham]

I'd vote against autowrapping Markdown. From my perspective:

• It can make minor changes lead to unnecessarily large diffs.
• It adds extra faff while editing - either you try to manually reflow text to keep to line length limit or have to apply a reformatter after making edits.
• Markdown unlike source code is generally naturally reflowable by soft wrapping as indentation is (mostly) not used to indicate structure.

[paddyroddy]

It can make minor changes lead to unnecessarily large diffs.

I actually wholeheartedly disagree with this bit. When markdown is not wrapped and someone changes a few words in a paragraph, it can be very long.

[samcunliffe]

I wrap markdown for my own stuff. But just because I quite like to cat flibble.md and read it in a terminal.
No strong opinion other than: if we do decide a policy of wrapping it should be linter-ed.