Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

changes the behavior of "" to makes things consistent #2149

Merged
merged 6 commits into from Jan 4, 2016

Conversation

justinbmeyer
Copy link
Contributor

fixes #2147 and #1762

This makes binding to an empty string "" in the scope work. But this changes the behavior of undefined. undefined values will be overwritten because the select's value will be "".

perhaps in a future release, we can support something like: <option {value}="undefined"/>

@justinbmeyer justinbmeyer added this to the 2.3.8 milestone Dec 23, 2015
@daffl daffl removed this from the 2.3.8 milestone Jan 4, 2016
daffl added a commit that referenced this pull request Jan 4, 2016
changes the behavior of ""  to makes things consistent
@daffl daffl merged commit e9bbfae into master Jan 4, 2016
@daffl daffl deleted the 2147-value-bound-to-emptystring branch January 4, 2016 17:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

option value as empty string are not selected with two way binding
2 participants