You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 29, 2019. It is now read-only.
If datepicker field set emty (for exemple, click "Clear" button in datepicker widget) in console write error: "Datepicker directive: "ng-model" value must be a Date object, a number of milliseconds since 01.01.1970 or a string representing an RFC2822 or ISO 8601 date." and form (with datepicker) be is not valid ($scope.form.$valid is false). I think, that empty (null) value for date field is not error! It's wrong.
The text was updated successfully, but these errors were encountered:
First I open my form with the datepicker. The Datepicker is empty, all ok. Then I choose some date, all is well. Then I decide to leave this field blank, press 'Clear' button... and that's a problem. In the console I see the error "Datepicker directive: "ng-model" value must be a Date object, a number of milliseconds since 01.01.1970 or a string representing an RFC2822 or ISO 8601 date." and my form with the date becomes invalid. It turns out that an empty value for a date field, this is a mistake. I think this is not right.
If datepicker field set emty (for exemple, click "Clear" button in datepicker widget) in console write error: "Datepicker directive: "ng-model" value must be a Date object, a number of milliseconds since 01.01.1970 or a string representing an RFC2822 or ISO 8601 date." and form (with datepicker) be is not valid ($scope.form.$valid is false). I think, that empty (null) value for date field is not error! It's wrong.
The text was updated successfully, but these errors were encountered: