This repository was archived by the owner on Oct 2, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
null values in ng-model after changing ng-model programmatically on multiselect #739
Comments
I got into some trouble when modifying the model outside of ui-select too |
I have the same proble than Kris Kesy |
+1 We are having the same problem. Spent quite a bit of time tracking this down. |
+1 |
3 similar comments
+1 |
+1 |
+1 |
We are also having the same issue. When is this pull request likely to be merged in? |
lisaq-leafnode
added a commit
to IntegratedBreedingPlatform/Workbench
that referenced
this issue
Mar 16, 2015
… variable details edit screen. There is a bug with multi-select being changed programmatically in the ui-select code so a fork of the code base that fixes the issue has been used temporarily. See angular-ui/ui-select#739 and KKrisu/ui-select@ec5c1e9 Issue: BMS-287 Reviewer: Helen
Should be fixed with #748 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
version 0.11.1
Demo http://plnkr.co/edit/kLsFtY?p=preview
settings multiselect, complex ui-select-choices objects
Issue
When ng-model is empty and I'm programmatically changing ng-model values, it changes ng-model to null. When ng-model is not empty and I'm changing values programmatically it works fine. That's why when you click on the button on my demo second time (or you choose any value manually using UI), the values are set correctly.
FIX
PR: #740
The text was updated successfully, but these errors were encountered: