Feature Request: Evaluate expression instead of [Items]

Currently to utilize ng-select we need to create a variable that needs to be alloted to [items] attribute. Only job of this variable is to act as a source for typeahead. The problem arises when there are multiple ng-select in a view. For each of these ng-select we need to define the input variables.

Instead we can have an attribute like source which evaluates an expression on change in input text. It can also handle async functions (promise). By having this in place we no longer have to handle and define input variables, cleaning up the component.

Incase the library goes this road there would also be a need to have a [debounce] attribute or a way to handle the same in component.

[anjmao]

Hi @shyamal890. Thanks for reporting. I was thinking about allowing [items] to accept Observable but I realised that you can use async pipe

source$: Observable<User[]>;
ngOnInit() {
     this.source$ = this.http.get('/users');
}

<ng-select [items]="source$ | async"></ng-select>

For all custom filtering needs there is [typeahead] input which allows you to implement any custom filtering you want on your side (debounce, distincUntilChanges, …). There are few improvements left for client side filtering like specifying which fields to search.

1. By allowing to pass data source expression ng-select will need to handle actual data retrieval this means you need to think what happens when error occurs, should ng-select handle it or not. This will add more complexity.

I’m adding this to version 2.0.0 milestone for now.

[varnastadeus]

In that case I am closing this issue, since having expression as @Input would result in this issues:

• Expression will mutate reference all the time and it will trigger cd
• Expression will stay immutable so user would need to mutate it which makes no sense