-
Notifications
You must be signed in to change notification settings - Fork 30k
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
build: add cpp linting to windows build #11856
Conversation
This PR adds cpp linting to windows build script. After this change, running command `vcbuild lint` will run both cpp linting and javascript linting on a windows machine. Fixes: nodejs#11816
vcbuild.bat
Outdated
@@ -362,6 +407,7 @@ echo running jslint-ci | |||
%config%\node tools\jslint.js -J -f tap -o test-eslint.tap benchmark lib test tools | |||
goto exit | |||
|
|||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unnecessary whitespace change
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks I will correct this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with the nit addressed
I am actually seeing linting failures on my machine when following steps in CONTRIBUTING.md. More specifically, the failure is regarding header_guard where the full file path is used for comparison. For example, for file "C:\sample\node\src\async-wrap.h", linter is expecting More of a question, I am wondering if specifying a |
thanks @bnoordhuis 👍 I changed file path comparison to use forward slash and it is now running fine. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, LGTM with a nit. CI: https://ci.nodejs.org/job/node-test-pull-request/6884/
tools/cpplint.py
Outdated
@@ -1074,7 +1074,8 @@ def RepositoryName(self): | |||
""" | |||
fullname = self.FullName() | |||
# XXX(bnoordhuis) Expects that cpplint.py lives in the tools/ directory. | |||
toplevel = os.path.abspath(os.path.join(os.path.dirname(__file__), '..')) | |||
toplevel = os.path.abspath( | |||
os.path.join(os.path.dirname(__file__), '..')).replace('\\', '/') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tiniest of nits: can you indent by four spaces?
Landed in 379eec3. |
@liusy182 So at the moment your Git author name and email address are set to:
People usually choose to use their full names for commits. To set your name globally (if you want to) you can do: git config --global user.name "Siyuan Liu" Just FYI. |
thanks @gibfahn I will change that in future. |
@liusy182 also your email address isn't associated with your GitHub account, so you probably want to either change your email address (see below), or add it as an alternative in your GitHub email settings. git config --global user.email "ss_161091@163.com" Otherwise you get "Unrecognised author" in the commit log. |
This PR adds cpp linting to windows build script. After this change, running command `vcbuild lint` will run both cpp linting and javascript linting on a windows machine. PR-URL: nodejs#11856 Fixes: nodejs#11816 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
This PR adds cpp linting to windows build script. After this change, running command `vcbuild lint` will run both cpp linting and javascript linting on a windows machine. PR-URL: nodejs#11856 Fixes: nodejs#11816 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing documenting new options
if /i "%1"=="test-known-issues" set test_args=%test_args% known_issues&goto arg-ok | ||
if /i "%1"=="test-node-inspect" set test_node_inspect=1&goto arg-ok | ||
if /i "%1"=="jslint" set jslint=1&goto arg-ok | ||
if /i "%1"=="jslint-ci" set jslint_ci=1&goto arg-ok | ||
if /i "%1"=="lint" set cpplint=1&set jslint=1&goto arg-ok | ||
if /i "%1"=="lint-ci" set cpplint=1&set jslint_ci=1&goto arg-ok | ||
if /i "%1"=="package" set package=1&goto arg-ok |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No documented in line 420 :(
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Addressed in #12278
* enable eslint to run even in a "clean" workspace * small improvement in performance by reducing number of calls to `findstr` * Document [jslint/jslint-ci] nodejs#11856 (comment)
should we backport to v6.x? edit: we should land with #11992 if we do |
* enable eslint to run even in a "clean" workspace * small improvement in performance by reducing number of calls to `findstr` * Document [jslint/jslint-ci] nodejs#11856 (comment)
This PR adds cpp linting to windows build script. After this change, running command `vcbuild lint` will run both cpp linting and javascript linting on a windows machine. PR-URL: nodejs#11856 Fixes: nodejs#11816 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
This PR adds cpp linting to windows build script. After this change, running command `vcbuild lint` will run both cpp linting and javascript linting on a windows machine. Backport-PR-URL: #14879 PR-URL: #11856 Fixes: #11816 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
This PR adds cpp linting to windows build script. After this change,
running command
vcbuild lint
will run both cpp linting and javascriptlinting on a windows machine.
Fixes: #11816
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)