Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: add blanks around code fences #29366

Closed
wants to merge 1 commit into from
Closed

Conversation

nschonni
Copy link
Member

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines

Addresses Markdownlint MD031 rule warnings
@nodejs-github-bot nodejs-github-bot added build Issues and PRs related to build files or the CI. doc Issues and PRs related to the documentations. labels Aug 29, 2019
@trivikr
Copy link
Member

trivikr commented Aug 30, 2019

@trivikr trivikr added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Aug 30, 2019
Copy link
Member

@devsnek devsnek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does our markdown linter have a rule we could enable for this?

@nschonni
Copy link
Member Author

nschonni commented Aug 30, 2019

The remark-lint equivalent is no-missing-blank-lines going by https://github.com/remarkjs/remark-lint/blob/master/doc/comparison-to-markdownlint.md, but I think it has some issues in that it doesn't ignore HTML comments and wants spaces for that too. It also requires the heading and lists spacing to be checked since it is one rule in that library

Edit: Markdownlint also flags the HTML comments trailing the headings

@Trott
Copy link
Member

Trott commented Aug 31, 2019

Landed in 9ab1e07

@Trott Trott closed this Aug 31, 2019
Trott pushed a commit that referenced this pull request Aug 31, 2019
Addresses Markdownlint MD031 rule warnings

PR-URL: #29366
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Gus Caplan <me@gus.host>
Reviewed-By: David Carlier <devnexen@gmail.com>
@nschonni nschonni deleted the fix-md031 branch August 31, 2019 22:44
BridgeAR pushed a commit that referenced this pull request Sep 3, 2019
Addresses Markdownlint MD031 rule warnings

PR-URL: #29366
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Gus Caplan <me@gus.host>
Reviewed-By: David Carlier <devnexen@gmail.com>
@BridgeAR BridgeAR mentioned this pull request Sep 3, 2019
BridgeAR pushed a commit that referenced this pull request Sep 4, 2019
Addresses Markdownlint MD031 rule warnings

PR-URL: #29366
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Gus Caplan <me@gus.host>
Reviewed-By: David Carlier <devnexen@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. build Issues and PRs related to build files or the CI. doc Issues and PRs related to the documentations.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants