ngList with uninitialised variable always fails validation with parse: true

[43081j]

since you started all this parse validation business, ngList no longer passes validation unless you initialise the variable it is bound to, to an empty array.

If we have an object:

$scope.model = {};

The HTML:

<input ng-model="model.foo" ng-list=", " name="foo" type="text">

foo will always invalidate the form until you enter something into it, even though it is not required. This shouldn't really be expected functionality as you may have large objects with many properties and only want to add them to the view, rather than some huge object setting them all to null/[].

This is because the ngList parser returns the initial undefined value, which then invalidates the input.

[Narretz]

I cannot reproduce this: http://plnkr.co/edit/eRnly9uIs8mgoUyaXyIX?p=preview with the latest snapshot

[43081j]

hmm strange, ill have a go at it later and post back if i can reproduce it again.

[43081j]

Here we go, it is when a directive validates the input before it has been touched.

http://plnkr.co/edit/Eyam8a7zQcKYIq7b3jni?p=preview

Because on validation, it runs any parsers I assume, which then returns undefined.

[Narretz]

Ah, I see. I think it's reasonable to return an empty array if the viewValue is undefined. There's unfortunately no real rule at the moment how strict the parse errors should be. But since the viewValue is basically empty, we should not set a parse error.

[43081j]

Is there any work around for this? Ideally I don't want to be implementing code for each field to return some default value. Before these parse changes it all worked fine.

I'm pretty much out of ideas now as both my main parser functions break validation simply by returning the passed value.

[Narretz]

In the meantime, you can define your own parser that will treat an undefined viewValue as an empty string: http://plnkr.co/edit/i57n9L76dzJHqG0kSynz?p=preview

Just make sure your parser runs before the ngList parser.