select in ng-repeat do not work

[joaoneto]

select in ng-repeat do not work

[joaoneto]

I just pushed a patch, could You test with this new version?

[GarPit]

I have a problem of using this plugin inside ng-repeat. Select was showed up twice.

[nguyer]

I am seeing the same thing as @GarPit

[GarPit]

Does anyone have a fix for this issue?

[joaoneto]

It's probably because of the version of the bootstrap-select, I'll set it version to 1.5.4 in bower.json to maintain compatibility.

see: https://github.com/joaoneto/angular-bootstrap-select/tree/v0.0.x

[joaoneto]

No it's not because of the version of the bootstrap-select, I reproduce that bug in http://codepen.io/joaoneto/pen/azoEdG

May be "ng-if" directive conflict... but I don't know what is happening
😞

[joaoneto]

Using "compile" function, ngIf, creates a new scope, it duplicates the DOM of bootstrap-select calling the .selectpicker('refresh') in postLink.

codepen fixed, now working with ng-repeat:
http://codepen.io/joaoneto/pen/azoEdG

"ngIf" docs explains: https://docs.angularjs.org/api/ng/directive/ngIf

Note that when an element is removed using ngIf its scope is destroyed and a new scope is created when the element is restored. The scope created within ngIf inherits from its parent scope using prototypal inheritance. An important implication of this is if ngModel is used within ngIf to bind to a javascript primitive defined in the parent scope. In this case any modifications made to the variable within the child scope will override (hide) the value in the parent scope.

c/c @nguyer, @GarPit

[GarPit]

So the decision is to use "link" instead of "compile", correct?

[joaoneto]

@GarPit correct,
Let's make some tests (we can use codepen), to consolidate this approach before release the version 0.1.0