[false] and [0] being treated as falsy in ngShow

[tmodrzynski]

I found out that for some reason, Angular parser (which is used e.g. to evaluate ngShow conditions) treats [false] and [0] (and their string counterparts: ['false'] and ['0']) as not true. This seems like a bug to me, because not empty array should never be treated as false in my opinion - even if it contains only falsy values.

On the other hand, [undefined] and [null] are treated as truthy. Same with arrays containing more than 1 element (['false', '0'], for example).

Browsers: Firefox 28, Chrome 34
OS: Ubuntu
Angular version: 1.2.16, 1.3.0-beta.5
Reproduction: Plunkr

[lgalfaso]

Hi, this is a duplicate of #4005. Closing this issue

[tmodrzynski]

Alright, thanks and sorry for making a commotion!

[lgalfaso]

@tmodrzynski It's all ok. This should be part of 1.3, the fact that it is not part of 1.2.x is because it needs a small breaking change.

BTW, an easy way to workaround this issue is to write <div ng-show="!!(foo)"></div>