Null filter not returning anything: filter:{category:null}"

[martijnve]

Dataset:

$scope.objs = [{name:'obj1', category:null}, {name:'obj2', category:null}, {name:'obj3', category:null}, {name:'obj4', category:1}, {name:'obj5', category:1}, {name:'obj6', category:1}, {name:'obj7', category:2}, {name:'obj8', category:2}, {name:'obj9', category:2}];

When i create an ng-repeat like this it returns the expected subset:
ng-repeat="obj in objs | filter:{category:1}"

But when i do this it does not show anything: (search for null instead of 1)
ng-repeat="obj in objs | filter:{category:null}"

This behaviour has been tested in 1.1.1 and 1.0.1 on chrome 23.0.1271.97 and IE9.

Plnkr and jsfiddle demo's:
http://plnkr.co/edit/jgfPPE
http://jsfiddle.net/KQYMY/17/

[wienand]

Substituting null with '!' works for me:

<span ng-repeat="obj in objs | filter:{category:'!'}">{{obj.name}}<br/></span>

http://plnkr.co/edit/azgQ0x

[martijnve]

Thanks that helps.

It's a hack though so i still think this needs to be fixed.

[pvasek]

Unfortunately, this is not working for values mapped from select which use ng-options and one default value (which has to be value="").

[btford]

As part of our effort to clean out old issues, this issue is being automatically closed since it has been inactivite for over two months.

Please try the newest versions of Angular (1.0.8 and 1.2.0-rc.1), and if the issue persists, comment below so we can discuss it.

Thanks!

[MartinodF]

This is still present in 1.2.0, is there any solution available when using ng-options besides writing a custom filter function?

[mvanroon]

I found that the only way to solve this problem is to manually write the <options>'s using ng-repeat and add a default option with value '!!'. This will result in the filter returning all items when the default is selected:

<select ng-model="recordsFilter.categoryId">
    <option value="!!">-- All categories --</option>
    <option ng-repeat="category in categories" value="{{category.id}}">{{project.title}}</option>
</select>

See this fiddle: http://jsfiddle.net/wiebl/jjC4H/

[umbrella-mikhail-menshinskiy]

+1. bug still presented in 1.2.0

[mstelten]

Another way to allow a null value in a filter object is to use this as a comparator:

$scope.allowNullValue = function (expected, actual) {
        if (actual === null) {
            return true;
        } else {
            // angular's default (non-strict) internal comparator
            var text = ('' + actual).toLowerCase();
            return ('' + expected).toLowerCase().indexOf(text) > -1;
        }
    };

<li ng-repeat="exr in exercises | filter:search:allowNullValue">
    // search ==> filter object i'm using
</li>

[rezen]

+1 Bug still present in 1.2.1 & 1.2.6

[kdekooter]

+1 still present in 1.2.8

Please reopen!

[luisfdeandrade]

• 1. I`m using 1.2.4 and this still happen

[alexandernst]

Still present

[davidjnelson]

Thanks to everyone for pointing this out as something to address! Looks like many people have said this is still present, reopening.