using the ng-model-options directive on a field (Angular 1.3+) prevents the initial value from being displayed

[jamesbrobb]

I've modified the example forms to demonstrate this issue.

The first commit shows the expected behaviour when setting an initial value within the django view. As you can see, every form displays 'james' within the first name field.

The second commit shows the broken behaviour once angular 1.3 and ng-model-options are used. As you can see, the initial value 'james' is no longer displayed.

I realise i've already submitted a fix for this (issue #127), but got a bit carried away refactoring my changes. So this is a closer fit to your original logic, using the actual ngModelController to set the value on the model.

[adrienbrunet]

@jrief I tried this, the behavior is still the same today. I went through the commits, the PR is ok. I never used debounce before but some folks could use it. t.It's merged now. Feel free to comment if you think something is wrong about it.