fix applying falsy options from config

[egmen]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

[coveralls]

Pull Request Test Coverage Report for Build 3800

• 2 of 2 (100.0%) changed or added relevant lines in 2 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 95.194%

---

Totals
Change from base Build 3710:	0.0%
Covered Lines:	4358
Relevant Lines:	4578

---

💛 - Coveralls

[kamilmysliwiec]

Thank you! Can you do the same fix for client classes (client-proxy etc)?

[egmen]

@kamilmysliwiec i'll wait nullish coalescing in TS 3.7 microsoft/TypeScript#26578 to fix this issue.
Ok?

[kamilmysliwiec]

Perhaps we should move forward with this issue now. We can always refactor after the update cc @egmen

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.