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

clear out const/let #9878

Closed
wants to merge 1 commit into from

Conversation

stpCollabr8nLstn
Copy link
Contributor

@stpCollabr8nLstn stpCollabr8nLstn commented Dec 1, 2016

Checklist
  • make -j8 test (UNIX), or vcbuild test nosign (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines
Affected core subsystem(s)

test

Description of change

change let to const/let
change assert.notEqual to assert

@nodejs-github-bot nodejs-github-bot added the test Issues and PRs related to the tests. label Dec 1, 2016
@imyller
Copy link
Member

imyller commented Dec 1, 2016

@stpCollabr8nLstn May I kindly ask you to format the commit message as described in CONTRIBUTING guidelines.

@mscdex mscdex added the tls Issues and PRs related to the tls subsystem. label Dec 1, 2016
@stpCollabr8nLstn
Copy link
Contributor Author

@imyller fixed

@imyller imyller added the code-and-learn Issues related to the Code-and-Learn events and PRs submitted during the events. label Dec 1, 2016
@imyller
Copy link
Member

imyller commented Dec 1, 2016

@stpCollabr8nLstn Thank you. Looks good 👍

@Trott
Copy link
Member

Trott commented Dec 1, 2016

var common = require('../common');
var assert = require('assert');
const common = require('../common');
const assert = require('assert');
Copy link
Member

Choose a reason for hiding this comment

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

Nit: I think it's ok to move the assert require after the common.hasCrypto check.

I'm pointing this out because other tests do this and it would be nice for consistency.
Thanks.

@gibfahn
Copy link
Member

gibfahn commented Dec 2, 2016

@stpCollabr8nLstn The commit author details have your name as amrios. Is this intentional? People normally use their full name.

@stpCollabr8nLstn
Copy link
Contributor Author

@gibfahn is there a way to retroactively change that?

@Trott
Copy link
Member

Trott commented Dec 2, 2016

@stpCollabr8nLstn

git commit --no-edit --amend --author="Jane Q. Public <email@example.com>"
git push --force-with-lease origin notMaster

To change it globally so it will be the default for future commits:

git config --global user.name "Jane Q. Public"

@stpCollabr8nLstn
Copy link
Contributor Author

thanks @Trott done

clear out const/let
change assert.notEqual to assert
move assert after common.hasCrypto check
@Trott
Copy link
Member

Trott commented Dec 3, 2016

Even though the code shouldn't have changed, it's probably a good practice to always re-run CI after a force push, so....

CI: https://ci.nodejs.org/job/node-test-pull-request/5135/

@targos
Copy link
Member

targos commented Dec 3, 2016

Landed in efa8456.

@targos targos closed this Dec 3, 2016
Copy link
Member

@jasnell jasnell left a comment

Choose a reason for hiding this comment

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

LGTM. Thank you for the PR and for participating in Code and Learn! Welcome to Node.js :-)

targos pushed a commit that referenced this pull request Dec 3, 2016
clear out const/let
change assert.notEqual to assert
move assert after common.hasCrypto check

PR-URL: #9878
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
addaleax pushed a commit that referenced this pull request Dec 5, 2016
clear out const/let
change assert.notEqual to assert
move assert after common.hasCrypto check

PR-URL: #9878
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
@Fishrock123 Fishrock123 mentioned this pull request Dec 5, 2016
2 tasks
addaleax pushed a commit to addaleax/node that referenced this pull request Dec 8, 2016
clear out const/let
change assert.notEqual to assert
move assert after common.hasCrypto check

PR-URL: nodejs#9878
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
jmdarling pushed a commit to jmdarling/node that referenced this pull request Dec 8, 2016
clear out const/let
change assert.notEqual to assert
move assert after common.hasCrypto check

PR-URL: nodejs#9878
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
MylesBorins pushed a commit that referenced this pull request Dec 21, 2016
clear out const/let
change assert.notEqual to assert
move assert after common.hasCrypto check

PR-URL: #9878
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
@MylesBorins MylesBorins mentioned this pull request Dec 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code-and-learn Issues related to the Code-and-Learn events and PRs submitted during the events. test Issues and PRs related to the tests. tls Issues and PRs related to the tls subsystem.
Projects
None yet
Development

Successfully merging this pull request may close these issues.