Fix Markdown linting #7
Merged
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
It would have been nice to keep the indicator as to the real reason for those warnings, "MD013" really does not tell anybody anything. Signed-off-by: Johannes Schindelin <[email protected]>
Actually: what the previous commit lamented about not being possible... _is_ possible! Yay! Signed-off-by: Johannes Schindelin <[email protected]>
|
@dennisameling could I bother you for a review? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What amounts to a late-night bug, I introduced a line into our Markdown linting configuration that is incorrect:
"MD013/line-length"does not work.The obvious solution is to remove the
/line-lengthsuffix, which makes it work.But we can do even better: those numbers ("MD013") are totally not intuitive. The labels are, however, and it is totally allowed to use them! So let's use them.