I’m probably missing the point too. Since an uninitialize boolean would be undefined, undefined == false, so that’s okay. undefined !== false, so that’s not okay.
Oh. One sec. I actually just tried it in JS and I see that undefined != false. That’s weird. I don’t think I ever realized this (or I forgot it long ago) so: var a; if(a) // is falsy if(a==true)//falsy but: if(a==false)//also falsy Harbs > On Jun 9, 2017, at 1:12 AM, Justin Mclean <jus...@classsoftware.com> wrote: > > Hi, > >> if (someBoolean === false) > > II think you may be missing the point? The issue is with: > > if (someBoolean == false) > > Not: > > if (someBoolean === false) > > Thanks, > Justin
