Closed lukekarrys closed 10 years ago
I agree it's a problem, not crazy about the fix at first glance. Seems like we could set the default to empty string or something instead. Not sure. The getString
thing just feels a bit too hackish, IMO.
@HenrikJoreteg I changed it so that when we set inputValue and startingValue we setting them to empty strings if they are falsy (and not 0) and not doing that inside the derived property.
looks good to me
In cases where you created an input view without a value and then later set the input to an empty string, it would report as
changed
which I don't think is what we want.Minor issue, but figured I'd give it a fix and a test.