not updating selected value if options are being loaded later about angular-selectize HOT 6 CLOSED

It's debatable, but I think this should be the expected behavior. Since a user cannot select an option before it exists, I don't think it should be possible programmatic-ally either.

from angular-selectize.

it's not possible on updating options list select item based on current state of related ng-model ?

from angular-selectize.

It's possible. I'll consider adding it. I'm just debating which is more expected behavior: the current one or the one you are suggesting. For now, you could wrap the part of your page that requires the options in <div ng-if='myOptions.length'></div>. So the block won't be rendered until the options are available

from angular-selectize.

yep, with ng-if all works like a charm. Thank you very much, now I can go sleep finally :) Ty for module again!

from angular-selectize.

You're welcome!

On Tue, Nov 18, 2014 at 5:28 PM, Alexey Smirnov [email protected]
wrote:

yep, with ng-if all works like a charm. Thank you very much, now I can go
sleep finally :) Ty for module again!

—
Reply to this email directly or view it on GitHub
#16 (comment)
.

from angular-selectize.

I also had this issue and I wonder what is the best practice, but I really don't feel like putting ng-if on all my inputs... Imagine the scenario where one would like to use a remote server to provide options to the select, a select can still have a default value even without loading the options from the server at the beginning no ? And also, if it is a multiple select, I can imagine that the options do not match the possible values all the time. If I select Iron man from a movie API and then start typing spid, the options returned from the server won't have Iron man among them but I don't want my value to be deselected.

from angular-selectize.