Closed hugovk closed 5 years ago
Ignoring "MD024/no-duplicate-heading/no-duplicate-header Multiple headings with the same content" because it complains about repeated headers like this, which I think are completely fine here:
...
...
...
...
If using VS Code, I recommend the markdownlint
(davidanson.vscode-markdownlint
) extension, it shows you linting errors with a squiggly green underline and tooltips.
Down to 404 errors:
5 MD006/ul-start-left Consider starting bulleted lists at the beginning of the line
13 MD007/ul-indent Unordered list indentation
208 MD013/line-length Line length
144 MD014/commands-show-output Dollar signs used before commands without showing output
2 MD028/no-blanks-blockquote Blank line inside blockquote
9 MD029/ol-prefix Ordered list item prefix
14 MD032/blanks-around-lists Lists should be surrounded by blank lines
1 MD034/no-bare-urls Bare URL used
7 MD036/no-emphasis-as-heading/no-emphasis-as-header Emphasis used instead of a heading
1 MD042/no-empty-links No empty links
@hugovk Awesome of you to pick this up! 😄I think your proposed strategy sounds good. If only the linter had a --fix
flag 😛
I actually asked a few months ago about that --fix
https://github.com/DavidAnson/vscode-markdownlint/issues/13#issuecomment-319719437 (for the VSC extension).
Any comments about the remaining errors? Fix, tweak or ignore?
5 MD006/ul-start-left Consider starting bulleted lists at the beginning of the line
13 MD007/ul-indent Unordered list indentation
208 MD013/line-length Line length
144 MD014/commands-show-output Dollar signs used before commands without showing output
2 MD028/no-blanks-blockquote Blank line inside blockquote
9 MD029/ol-prefix Ordered list item prefix
14 MD032/blanks-around-lists Lists should be surrounded by blank lines
1 MD034/no-bare-urls Bare URL used
1 MD042/no-empty-links No empty links
You can see the context from https://travis-ci.org/sb2nov/mac-setup/builds/478347674#L457.
If not, I'll disable those for the time being.
I think we can use allow_failure https://docs.travis-ci.com/user/customizing-the-build/#rows-that-are-allowed-to-fail instead of disabling the rules.
If we allow failures then new PRs will introduce new linting errors and no-one will notice.
A build failure is a sure way to prevent new errors.
I'd be happy to ignore the rest and we can work through them one-by-one. It's not like these linting errors are critical in any way. Great work on this PR!
Maybe we can ignore MD013 (Line length).
And we're green!
Fixes #239.
This installs and runs the command-line interface for markdownlint.
Well, at the moment, there's a LOT of lint errors!
https://travis-ci.org/hugovk/mac-setup/builds/478022235#L754
643 to be exact:
Here's a count by category:
Are there any of these that should definitely be turned off right away? Or any that can be adjusted (eg. increase
line-length
a bit)?I'd suggest tweaking the config a bit, fixing a few of the low-hanging fruit, then temporarily ignoring the others to get the CI to pass. Then the others can be tackled in batches one-by-one in their own PRs.