also found useful this pattern as more declarative, but need to use it carefully. my early pitfall was to use array.length && ... instead of array.length === 0 && ...
This is great advice. Falsey and Thruthy values bit me in the same way. I do things like isEmpty(array) or if I am really defensive isNullOrEmpty(array)
Thank you @selbekk for the thorough "10 component commandments".
I am not sure if this is a tip or a bad practice, but I've started seeing a lot of code with following structure in "return/render" methods.
Would such a way of showing components a bad practice?
I found it more declarative then having "if/else" (or using a ternary operator).
But the downside I found is that, many people aren't familiar with how to interpret the "state && component".
What would you think?
I had the same question 🤔
also found useful this pattern as more declarative, but need to use it carefully. my early pitfall was to use array.length && ... instead of array.length === 0 && ...
What about just using
!!array.length && ...?
It looks smarter and shortly.
yep, it's shorter :) use !! many years while coding on perl. now I prefer Boolean(array.length)
What about just using !!array.length && ... ? It looks smarter and short.
This is great advice. Falsey and Thruthy values bit me in the same way. I do things like isEmpty(array) or if I am really defensive isNullOrEmpty(array)
It's the short-circuit operator. I think it's neat.
Does eslint still flag it?