yes, that is a solid logic, one that I also applied and expected to be the result.

that is until a Vue component started complaining that I am passing in a number for a prop that expects a boolean.

turns out the result of that code is actually: 0, because javascript

of course if you flip it and try

false && 0 && 1

then you get false, because that's what you really want in a language, where && behaves differently depending on what is on what side.