@b_ez_man@mileswjohnson@yavascript Yeah, I mean it all depends on what you’re doing I guess. With third party APIs I agree, at Netflix we basically never made anything non-nullable in third party APIs to avoid access errors. In first party apps, I think I’d make the argument that it’s useful to have access errors.
@mileswjohnson@b_ez_man@yavascript I don't really get it. I mean some graphs just return null fields when you can't access something, which sounds similar to this. But for non-null fields, wtf do you do right
Normalize pineapple on pizza.
Normalize pineapple on pizza.
Normalize pineapple on pizza.
Normalize pineapple on pizza.
Normalize pineapple on pizza.
Normalize pineapple on pizza.
TIL that svg's render via document order and so I can't use zindexs... To fix this issue where the 2nd part of a progress bar was overlapped on top of the 1st part, I basically flipped the order in which I rendered them and then used transform: scaleX(-1). DUMB CODE WORKS!