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

tools,test: apply markdown linting to test dir #22221

Closed
wants to merge 5 commits into from

Conversation

Trott
Copy link
Member

@Trott Trott commented Aug 9, 2018

Enable markdown linting of the test directory. This change is applied
only to Makefile and not vcbuild.bat because we do not currently lint
anything outside of the doc directory using vcbuild.bat. In the
Makefile, the other targets are called "misc" but that feature does not
currently exist in vcbuild.bat. Adding it would be good, but outside the
scope of this change.

@vsemozhetbyt

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • documentation is changed or added
  • commit message follows commit guidelines

Add first-level header to .md file in fixture directory. The file in
question is documentation for the fixture and is not part of any tests.
This is in prepration for markdown linting of the `test` directory.
In preparation for markdown linting of files in the `test` directory,
make sure all lines in `test/common/README.md` are no more than 80
characters long.
First header should be a first-level header according to our lint rules.
Make it so in prepartion for applying the markdown linting to the test
directory.
In preparation for applying markdown linting to the `test` directory,
adjust the table in `test/README.md` to comply with our markdown rules.
Enable markdown linting of the test directory. This change is applied
only to Makefile and not vcbuild.bat because we do not currently lint
anything outside of the doc directory using vcbuild.bat. In the
Makefile, the other targets are called "misc" but that feature does not
currently exist in vcbuild.bat. Adding it would be good, but outside the
scope of this change.
@nodejs-github-bot nodejs-github-bot added the build Issues and PRs related to build files or the CI. label Aug 9, 2018
@Trott Trott mentioned this pull request Aug 9, 2018
4 tasks
@Trott
Copy link
Member Author

Trott commented Aug 9, 2018

|v8-updates |No |Tests for V8 performance integration.|
| Directory | Runs on CI | Purpose |
| ------------------- | --------------- | --------------- |
| `abort` | Yes | Tests for when the ``` --abort-on-uncaught-exception ``` flag is used. |
Copy link
Member

Choose a reason for hiding this comment

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

Out of interest, are the added backticks for the Directory column because of the linter or a stylistic change?

Copy link
Member Author

Choose a reason for hiding this comment

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

It's a clunky workaround for the linter flagging bare-text v8. If it sees v8 in backticks, it assumes it's part of code or a directory listing or something like that, but if it sees it bare, it flags it as a prohibited string and assumes you meant V8 instead.

I actually do think the directory names should be in backticks, but I also acknowledge that's a debatable position. :-D

Copy link
Member

Choose a reason for hiding this comment

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

Thanks for the explanation. I'm okay with the backticks, it just wasn't obvious to me why they were added.

@Trott Trott added tools Issues and PRs related to the tools directory. test Issues and PRs related to the tests. doc Issues and PRs related to the documentations. and removed test Issues and PRs related to the tests. labels Aug 9, 2018
Copy link
Contributor

@sagirk sagirk left a comment

Choose a reason for hiding this comment

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

LGTM! 🎉

Copy link
Contributor

@XadillaX XadillaX left a comment

Choose a reason for hiding this comment

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

LGTM!

@maclover7 maclover7 added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Aug 10, 2018
Trott added a commit to Trott/io.js that referenced this pull request Aug 12, 2018
Add first-level header to .md file in fixture directory. The file in
question is documentation for the fixture and is not part of any tests.
This is in prepration for markdown linting of the `test` directory.

PR-URL: nodejs#22221
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Jon Moss <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
Reviewed-By: Khaidi Chu <[email protected]>
Reviewed-By: Daniel Bevenius <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: George Adams <[email protected]>
Trott added a commit to Trott/io.js that referenced this pull request Aug 12, 2018
In preparation for markdown linting of files in the `test` directory,
make sure all lines in `test/common/README.md` are no more than 80
characters long.

PR-URL: nodejs#22221
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Jon Moss <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
Reviewed-By: Khaidi Chu <[email protected]>
Reviewed-By: Daniel Bevenius <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: George Adams <[email protected]>
Trott added a commit to Trott/io.js that referenced this pull request Aug 12, 2018
First header should be a first-level header according to our lint rules.
Make it so in prepartion for applying the markdown linting to the test
directory.

PR-URL: nodejs#22221
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Jon Moss <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
Reviewed-By: Khaidi Chu <[email protected]>
Reviewed-By: Daniel Bevenius <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: George Adams <[email protected]>
Trott added a commit to Trott/io.js that referenced this pull request Aug 12, 2018
In preparation for applying markdown linting to the `test` directory,
adjust the table in `test/README.md` to comply with our markdown rules.

PR-URL: nodejs#22221
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Jon Moss <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
Reviewed-By: Khaidi Chu <[email protected]>
Reviewed-By: Daniel Bevenius <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: George Adams <[email protected]>
Trott added a commit to Trott/io.js that referenced this pull request Aug 12, 2018
Enable markdown linting of the test directory. This change is applied
only to Makefile and not vcbuild.bat because we do not currently lint
anything outside of the doc directory using vcbuild.bat. In the
Makefile, the other targets are called "misc" but that feature does not
currently exist in vcbuild.bat. Adding it would be good, but outside the
scope of this change.

PR-URL: nodejs#22221
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Jon Moss <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
Reviewed-By: Khaidi Chu <[email protected]>
Reviewed-By: Daniel Bevenius <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: George Adams <[email protected]>
@Trott
Copy link
Member Author

Trott commented Aug 12, 2018

Landed in d3d5982...7cec27c

@Trott Trott closed this Aug 12, 2018
rvagg added a commit that referenced this pull request Aug 13, 2018
#20894 / 2930bd1 was introduced on
master which removed an offending line in this doc before linting was
applied to test/ in #22221 /
56103ab. Since 20894 is semver-major, the full changes were not
backported.

PR-URL: #22296
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
Reviewed-By: George Adams <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
rvagg added a commit that referenced this pull request Aug 15, 2018
#20894 / 2930bd1 was introduced on
master which removed an offending line in this doc before linting was
applied to test/ in #22221 /
56103ab. Since 20894 is semver-major, the full changes were not
backported.

PR-URL: #22296
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
Reviewed-By: George Adams <[email protected]>
Reviewed-By: Vse Mozhet Byt <[email protected]>
@Trott Trott deleted the lint-md-test branch January 13, 2022 22:50
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. tools Issues and PRs related to the tools directory.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants