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

deps: Use '===' instead of '==' #22970

Closed
wants to merge 1 commit into from
Closed

deps: Use '===' instead of '==' #22970

wants to merge 1 commit into from

Conversation

ghost
Copy link

@ghost ghost commented Sep 20, 2018

To use '===' instead of '==' in union, because all the other js files are using '===' for the strict equal comparation.

  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines

Considering it's a good habit to use '===' instead of '==', and we've
used 'eslint' to have to a check for all the js files inside 'lib'.
However those in 'deps' haven't been checked yet.
@nodejs-github-bot nodejs-github-bot added the v8 engine Issues and PRs related to the V8 dependency. label Sep 20, 2018
@tniessen
Copy link
Member

tniessen commented Sep 20, 2018

Thank you, @Maledong! We usually do not touch files in deps/ unless we are cherry-picking upstream changes or need to adapt the dependency to the requirements of Node.js.

You can suggest this change to the respective upstream repositories, but there are people who prefer to use == with typeof since both sides are guaranteed to be of the same type.

Also, please do not capitalize the verb in your commit messages as already noted in #22858 (comment).

@tniessen tniessen closed this Sep 20, 2018
@ghost ghost deleted the Using=== branch September 20, 2018 10:24
@ghost
Copy link
Author

ghost commented Sep 20, 2018

OK, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v8 engine Issues and PRs related to the V8 dependency.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants