Enforce 80-character line limit in all markdown files #4321
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jtraglia
force-pushed
the
markdown-line-wrap
branch
from
1fc2229 to
03c4ea2
Compare
jtraglia
changed the title
GabrielAstieres
approved these changes
May 16, 2025
Contributor
GabrielAstieres
left a comment
GabrielAstieres
left a comment
There was a problem hiding this comment.
LGTM thanks Justin
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR wraps lines in markdown files (specs) at 80 characters. This helps with consistency & readability when viewing raw markdown, which contributors often do when making changes. I've reviewed a large chunk of these changes and everything appears to be fine to me. I like that it doesn't break hyperlinks, doesn't break inline code, and indents wrapped lists.
There are no other changes here. I simply added
--wrap=80and ranmake lint.PS: this is something I've been wanting to do for a while. Waited until after the v1.5.0 stable release. We're going to do a new alpha release next week with a few spec changes, so I believe now is a good time for this.