Dropdown not populating when options are resolved after model.

[zackarychapple]

Related to #128,

I found this issue when I was trying to bind my dropdown to an object on my model. It worked locally but when I deployed to one of the servers the dropdowns never pre-selected. Eventually I found that the model was being resolved before the constants I was using for the dropdown values were resolved. This caused the page to render with no values pre-selected, however the values were there when selecting an option. I resolved this by not populating the model until the promise for the constants resolved.

Is there a better way to manage this internally with ui-select, or should I always resolve the constants(values of the select) before populating the model it is matched against?

[dimirc]

@zackarychapple can you try to setup a plunker to reproduce this situation so I can try solving faster?

[dimirc]

I think with this plunker I'm reproducing the problem. I'm just using a timeout of 5 secs and if pressing "Change Model", it wont show the match correctly selected when timeout populates the choices.

[zackarychapple]

That is what I was seeing. Any hopes of putting something in for that or adding to the documentation?

[dimirc]

I think maybe there's a solution for this, I'm checking it

[dimirc]

@zackarychapple check #134

[zackarychapple]

Fantastic, works very well. @dimirc thank you again. Might want to bump version. I had to remove the bower directory to get this to pick up.

[dimirc]

@zackarychapple new v0.5.3 released