| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
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
| %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.
Unnecessary whitespace change
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks I will correct this.
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM with the nit addressed
Sorry, something went wrong.
|
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 #ifndef SAMPLE_NODE_SRC_ASYNC_WRAP_H_ instead of #ifndef SRC_ASYNC_WRAP_INL_H_. This is because _root is empty on my machine so this statement is not executed. More of a question, I am wondering if specifying a --root when calling cpplint.py is required. I do not have a Mac at hand so I am not sure how linting could pass on Mac. |
Sorry, something went wrong.
|
thanks @bnoordhuis 👍 I changed file path comparison to use forward slash and it is now running fine. |
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks, LGTM with a nit. CI: https://ci.nodejs.org/job/node-test-pull-request/6884/
Sorry, something went wrong.
| # 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.
Tiniest of nits: can you indent by four spaces?
Sorry, something went wrong.
|
@liusy182 So at the moment your Git author name and email address are set to: liusi <siyuan.liu@autodesk.com> 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. |
Sorry, something went wrong.
|
thanks @gibfahn I will change that in future. |
Sorry, something went wrong.
|
@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. |
Sorry, something went wrong.
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.
Missing documenting new options
Sorry, something went wrong.
| 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.
No documented in line 420 :(
Sorry, something went wrong.
There was a problem hiding this comment.
Addressed in #12278
Sorry, something went wrong.
* 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 |
Sorry, something went wrong.
* 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>
| Back | FazBrowse Home | New Git URL |
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: #11816
Checklist
Affected core subsystem(s)