One potential problem I can see from this approach is that js symbols convert to true. Which means it can confuse people when used like this:
const None = Symbol(`None`); if (None) console.log('Oopsie');
Yeah, I see that point. However, with so many falsy values in JS, I would not use the same for null or undefined either.
null
undefined
const value: string | null | undefined = … if (value) { /* a non-empty string – intention or oversight? */} if (value == null) { /* a string */ }
Maybe NaN is a better choice? :D
NaN
Actually, I was caught off guard by empty strings a few times before. You have a good point.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
One potential problem I can see from this approach is that js symbols convert to true. Which means it can confuse people when used like this:
Yeah, I see that point. However, with so many falsy values in JS, I would not use the same for
nullorundefinedeither.Maybe
NaNis a better choice? :DActually, I was caught off guard by empty strings a few times before. You have a good point.