If an attribute is null, I would prefer to simply not serialize it.
That’s interesting. I’m on the opposite team. If a customer model defines an optional birthday, for instance, I’d rather have it serialized as a null value if it’s not available for a specific customer.
Indeed, and that turns out to be a problem if the JavaScript expects the key not to be there, but instead it is there. And then you try to tell the backend dev that the key shouldn’t be there, but he’ll try to convince you that it’s the same whether the key is not there or whether it’s assigned null and then you wonder if he’s messing with you, but actually he isn’t and then the only thing keeping you sane is bitching about it in meme form on lemmy.
I used to think that at least the parts that are Fairtrade wouldn’t be affected as much.
I’m not saying WalMart wouldn’t do this on purpose (because I have never interacted with them), I can tell you as a software developer that’s it’s entirely possible for a single functionality of an app to malfunction while everything else works.
Never attribute to malice that which is adequately explained by stupidity.
Chocolate production is infested with slave labor, child labor and child slave labor.
For long hair it helps with combing. Just like the old silicone spray for ballpoint mice, it reduces friction with the comb.
If I can control my fans and my GPU in Linux the way I can in Windows I will.
To be fair, just because
obj.foois undefined, that doesn’t mean the key is missing. It could also be assigned the value undefined.const obj = { foo: undefined }vsconst obj = {}