You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
Upgraded to 1.3.15 today in one of my apps and found that an ng-repeat option list with a filter no longer displayed any items. It appears the problem is due to the fact the initial string filter value is null - if I change the initial value to an empty string it works.
// intial view model value that doesn't workvm.searchText=null;vm.resourceList=[{ResourceId: "Add", Style=null},{ResourceId: "Add_Title",Style="margin-left: 10px"},
...
];
Then in the HTML to bind:
<optionng-repeat="resource in view.resourceList | filter:view.searchText"
value="{{resource.ResourceId}}"
style="{{resource.Style}}">
{{resource.ResourceId}}
</option>
If the intial value of searchText is null the list will not display any items. If the initial value is an empty string (""), however it works fine. This is a breaking change from 1.3.14 where this worked. If by design this should probably go into the breaking change list.
However I think null should be treated like an empty string for search filters I believe so I'd call this a bug...