Cannot select option when bind data dynamic into nb-select

[tuannh2]

I'm using nb-select for my project, and when i bind data auto in nb-select, i cannot select option as below images:

my code in component:

"
import { Component } from '@angular/core';
import { NbMenuService } from '@nebular/theme';
import { TaxAuthorityService } from '../../@core/services/taxAuthority.service';

@component({
selector: 'ngx-organization',
styleUrls: ['organization.component.scss'],
templateUrl: 'organization.component.html',
})

export class OrganizationComponent {
taxAuthorities;

constructor(private menuService: NbMenuService, private taxAuthorityService: TaxAuthorityService) {
    //this.taxAuthorities = taxAuthorityService.getTaxAuthorities();
}

ngOnInit() {
    this.taxAuthorityService.getTaxAuthorities().subscribe(p=>this.taxAuthorities = p);
}

}
"

Thanks!

Tuan,

[gaspardip]

Its already fixed by #1009 but Nebular 3.0.1 is not complete yet

Duplicates: #948 #931

[tanzeelrana]

is this fix released ?

[tuannh2]

Thanks @tanzeelrana.

I already used the normal select control instead of nb-select.

Tuan,

[jaapcrezee]

This does not seem fixed in Nebular v3.3.0. When I set my .ts property to = null and use data subscription and

  <nb-select *ngIf="items">
    <ng-container *ngFor="let item of items">
      <nb-option>{{ item }}</nb-option>
    </ng-container>
</nb-select>

there is no data in the dropdown select; <select/> works as expected.

[nnixaa]

@Tibing can you check?

[aefox]

the initially raised issue with selecting the option actually works as expected as long as your nb-options correctly set their value attribute. please see this stackblitz for examples. If you remove the [value]="item" on the nb-options you'll see the problem you mentioned reproduces. but this is an incorrect usage of nb-option. cc: @nnixaa maybe this needs better documentation?

In the second case when using an ng-container as wrapper for nb-options the problem is indeed reproducible on nebular 3.1.0 and 3.3.0. I already have a fix and currently writing some tests. Will raise PR today

[aefox]

PR raised

[sutra]

It seems that, this issue can be reproduced in 3.0.0, and fixed in 3.0.1.