One-way binding broken after 1.0.0-beta.1.0.3 update

[michaelmalonenz]

After updating to yesterday's release, we found an issue regarding one-way binding. Specifically, if using a getter to compute the value from another object, if the value is undefined (which it must be to show the placeholder) then the literal string undefined is shown in the input. If the binding is changed to two-way (and a setter added, obviously) then the problem disappears.

I have reproduced the problem here:
https://github.com/michaelmalonenz/skeleton-navigation/tree/one-way-binding-bug

[EisenbergEffect]

@jdanyow Seems like a small regression.

[jdanyow]

ah yes- will get this fixed. This logic that was added for #152 needs to be added to the static accessor stuff.