Do your code ever do things differently based on if a variable contains a null or if it contains a undefined?
Let me try a bad analogy: If couldYouBuyMeSomeFlowers() returns null, it would be reasonable to assume that the florist is out of flowers (why else would he give us an explicit null instead of nothing).. But if it returns undefined.. Did the method forget to go to the florist? Should i call couldYouBuyMeSomeFlowers() again until it returns flowers or null? Or is the florist gone? No matter the reason, I still don't have flowers and I will have to throw a PartyCanceledError("Sorry, we can't have a party without flowers").
PartyCanceledError("Sorry, we can't have a party without flowers")
If i needed a reason why the method failed, it would be better if the method just threw an error instead. StoreNotFoundError or NotEnoughMoneyError. Or a Promise<Flower> for a later delivery. I could deal with that.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.