This repository has been 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
Clearing the selection sets model value to 'undefined' #863
Labels
Comments
+1 |
+1 |
+1 |
Please do not +1 it creates unnecessary noise in issues, use github reactions. This looks like a small change, it could probably be fixed in a quick PR with associated unit test. Instead of +1'ing consider submitting a PR! 😃 |
jrbotros
pushed a commit
to jrbotros/ui-select
that referenced
this issue
Apr 5, 2017
jrbotros
pushed a commit
to jrbotros/ui-select
that referenced
this issue
Apr 5, 2017
jrbotros
pushed a commit
to jrbotros/ui-select
that referenced
this issue
Apr 5, 2017
jrbotros
pushed a commit
to jrbotros/ui-select
that referenced
this issue
Apr 5, 2017
jrbotros
pushed a commit
to jrbotros/ui-select
that referenced
this issue
Apr 5, 2017
jrbotros
pushed a commit
to jrbotros/ui-select
that referenced
this issue
Apr 5, 2017
BTW, the fix for this broke code for those waiting for This was definitely a breaking change and should have been released in new major version... |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Clearing the selection in a non-multiselect which has the "allow-clear" attribute sets the model value to undefined, while the expected value would be null.
Being undefined causes Angular to ignore the change, so it won't be sent to the server.
The text was updated successfully, but these errors were encountered: