Skip to content

Conversation

@Trott
Copy link
Member

@Trott Trott commented Aug 16, 2016

Checklist
  • make -j4 test (UNIX), or vcbuild test nosign (Windows) passes
  • commit message follows commit guidelines
Affected core subsystem(s)

test timers

Description of change

Use === instead of == in pummel/test-timers.js

@Trott Trott added timers Issues and PRs related to the timers subsystem / setImmediate, setInterval, setTimeout. test Issues and PRs related to the tests. labels Aug 16, 2016
@addaleax
Copy link
Member

Love the PR title. ;)

LGTM… how bad would it be to do all of those in a bulk update?

@Trott Trott changed the title test: favor == over == in test-timers.js test: favor === over == in test-timers.js Aug 16, 2016
Use `===` instead of `==` in pummel/test-timers.js
@Trott
Copy link
Member Author

Trott commented Aug 16, 2016

@addaleax asked:

how bad would it be to do all of those in a bulk update?

Hard to say. Might be fine. Or it might be hard to review because it will be a mix of:

  • == -> ===
  • != => !==
  • == -> assert.strictEqual()
  • == -> assert.deepStrictEqual()
  • != -> assert.notStrictEqual()
  • != -> assert.notDeepStrictEqual()
  • watching out for legitimate uses of == and != that shouldn't be changed (like in assert.js)

It will probably be more straightforward in the tests than in the instances in lib.

I was pondering both doing one big PR and also going the other way and suggesting that people do individual files as a good first contribution.
¯_(ツ)_/¯

@addaleax
Copy link
Member

@Trott Mh yeah, you can probably judge that best. It just seems like a lot of overhead on your part to me. :)

CI: https://ci.nodejs.org/job/node-test-commit/4610/

@targos
Copy link
Member

targos commented Aug 17, 2016

LGTM

2 similar comments
@cjihrig
Copy link
Contributor

cjihrig commented Aug 17, 2016

LGTM

@jasnell
Copy link
Member

jasnell commented Aug 17, 2016

LGTM

Trott added a commit to Trott/io.js that referenced this pull request Aug 18, 2016
Use `===` instead of `==` in pummel/test-timers.js

PR-URL: nodejs#8131
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: James M Snell <[email protected]>
@Trott
Copy link
Member Author

Trott commented Aug 18, 2016

Landed in d52ceb4

@Trott Trott closed this Aug 18, 2016
evanlucas pushed a commit that referenced this pull request Aug 24, 2016
Use `===` instead of `==` in pummel/test-timers.js

PR-URL: #8131
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: James M Snell <[email protected]>
MylesBorins pushed a commit that referenced this pull request Oct 10, 2016
Use `===` instead of `==` in pummel/test-timers.js

PR-URL: #8131
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: James M Snell <[email protected]>
rvagg pushed a commit that referenced this pull request Oct 18, 2016
Use `===` instead of `==` in pummel/test-timers.js

PR-URL: #8131
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: James M Snell <[email protected]>
MylesBorins pushed a commit that referenced this pull request Oct 26, 2016
Use `===` instead of `==` in pummel/test-timers.js

PR-URL: #8131
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: James M Snell <[email protected]>
@MylesBorins MylesBorins mentioned this pull request Oct 26, 2016
@Trott Trott deleted the timerpummel branch January 13, 2022 22:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

test Issues and PRs related to the tests. timers Issues and PRs related to the timers subsystem / setImmediate, setInterval, setTimeout.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants