Is there a special reason to do:
if (!options || (options && options.booleanCondition))
Instead of:
if (!options || options.booleanCondition)
I’m no javascript guru, so perhaps there’s a special case or reason why the author of that code wrote it that way.
i don’t see a reason to do
I’m no Guru but i’d stick to
and save a check to the fact that options is true: in fact if
optionsis not true the first condition istrueand the second is never evaluated since it’s anorcondition.That’s what i think