Use === in generated code

[abatilo]

Using === is recommended in modern JavaScript / TypeScript since it also
verifies for typing without any implicit conversions

[google-cla]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[abatilo]

@atreya2011 @lyonlai Could I ask you for a review?

[lyonlai]

sure that seems reasonable. I think you will need to sign the google-cla before contributing to the project. @abatilo

[lyonlai]

nvm about the google-cla. looks like you've done that.

[lyonlai]

Good pick. not sure how this is missed.

[atreya2011]

@abatilo Hey, sorry for the delay. I am not the maintainer and rather a contributor to this project so @lyonlai is the right person to ask for a review. And it seems like this PR is already merged 🎉

[lyonlai]

@abatilo found that there's an extra trigger google cla commit. didn't notice the extra commit but I've fixed it in master. if you run into problem with it just re-pull the master.

it is understandable but also if next time you could at your branch, just git commit --amend -C HEAD and do a force push to the branch it should retrigger the check.

[abatilo]

That makes sense, thank you very much for the tip! That'll save me from the empty commits in the future!