"if" helper considers 0 to be a falsy value

[artiee]

The if-helper seems to consider value 0 (zero) to be falsy because the simple "!conditional" -test is used. This creates problems with many apps as 0 should be considered as a real value. The falsy values should be 'undefined', null, false, '', [], and {}.

Also the Utils.isEmpty seems to recheck that value isn't 0. This seems unnecessary.

[gnclmorais]

If this gets accepted, can you please add this behaviour to the documentation (i.e. write that 0 is not a falsy value)? I ask this because, as a JavaScript developer, I would kind of expect 0 to be evaluated as falsy... And thus it would be clearer for everybody. Thank you.

[kpdecker]

@artiee @gnclmorais See #608 for discussion on this. After checking the new behavior for the upcoming alpha release I am worried that this will break almost all code that is out there already and the expectations of javascript developers as @gnclmorais notes.

[kpdecker]

Released in 1.1.0