Using the value binding on an input can produce 'undefined' in the input about binding HOT 2 CLOSED

The current behavior has a few things going for it:

• Doesn't require any custom code to handle "throw on undefined prop in input value binding"
• You can see the property is undefined without having to look at the console
• People can override the standard behavior with a value converter if they want to coalesce the model value <input value.bind="myModel.doesNotExist | coalesce:'' " />
• There will be a way to configure the Aurelia binding system to throw when binding to undefined properties: #30

from binding.

Yes, I have to agree with your points, it used to annoy me in knockout when the binding failed, it threw an error then failed to bind anything else.

One downside to aurelia's current approach is for large forms when binding to a large model. When creating something new, you would have to specify each and every property to be an empty string on your model for example or add a converter to every field (the converter may be the best approach for this IMO). This could add some verbosity to the code however and it's another thing to maintain. I think the plus points you described above however out weigh this negative impact.

from binding.