Closed rijk closed 3 years ago
Rebased on your latest push.
I'm not apposed to this, but maybe null
instead? In Typescript null
makes more sense, and of course, any "falsy" value will work just fine in JS. This is a great addition.
I think this has been superseded by other decisions.
May I suggest we add
false
as well? It already works (the code does a falsy check), and in some cases it allows for cleaner code — up to the user's preference of course:You don't have to use it like this, but as the code allows it I see no reason for Typescript to give a warning. Hope you'll consider. Thanks!