Timestamp treated as invalid model value in datepicker

[oliversalzburg]

The datepicker directive says ng-model can be "a number of milliseconds since 01.01.1970". However parseData will not treat such an input as valid.

[bekos]

@oliversalzburg Can you provide a plunker with your issue?

[oliversalzburg]

@bekos Yeah, sorry for not providing one earlier. I just modified the demo plunkr: http://plnkr.co/edit/yDcTUvs7H1xkqJ7XWPBq?p=preview

Please note the paragraph indicating "There is an error in your form.". If I set dt to new Date() instead, the paragraph is not shown.

Interestingly, I still see the paragraph if I use $scope.dt = new Date(1234567890000);. So, I don't think parseData not accepting ints actually has anything to do with it.

[krimple]

This was bugging us in my training class... I used a Date.now() to generate a time, which Angular can process with a {{ myDate | date:'MM/dd/yyyy' }} template. It was a good exercise for our students to solve, but am curious if this is this on deck for a fix soon? I switched to doing new Date() instead which worked for now but it would be nice to be able to handle a timetick version of the date like Angular's filter does.

[shawa8]

+1

[andreacremese]

I ran into a similar snag with angular + UI-bootstrap to both initialize and style the content of datepicker input at the same time on load in the controller.

Long story short:

• Initialize as new Date(): the form with datepicker is VALID but datetime styling is NOT APPLIED.
• Initialize as Date().now: the form with datepicker is NOT VALID but datetime styling is APPLIED.

Noting that Date.new() returns the number of milliseconds from 1970 (not accepted by datetime) and new Date() returns a JS Date Instance (accepted by DateTime, but not styled properly), the solution was to initialize the variable in the scope to an ISO 8601 string:

var date = new Date();  
$scope.boundVariable = date.toISOString();

ISO string is apparently what datetime binds to the $modelValue of the form.

Interestingly, when using new Date() as initializer, the $viewValue and the $modelValue for the form diverged ($viewValue was a time stamp object, $modelValue was the ISO string). The solution (or workaround) basically initializes the $viewValue coherently with the $modelValue.

[nirre7]

+1

[delwyn]

+1

[haoqunjiang]

+1

[karianna]

Hi @oliversalzburg - is this with both Angular 1.2.x and 1.3.x?

[oliversalzburg]

@karianna I haven't tested this since I reported it. We just moved to a different approach. 1.3 wasn't released when I reported it, but I don't see why the behavior would have changed.

[khashayar]

I've added the following line on top of parseDate():

if (angular.isNumber(viewValue)) {
  viewValue = new Date(viewValue);
}

Then it goes through the if/else chain and falls into

} else if (angular.isDate(viewValue) && !isNaN(viewValue)) {

which handles it correctly.

Updated Plunker

As an alternative we can have this check on if/else chain itself but I didn't want to repeat that part of the chain again.

@karianna Please let me know if you're ok with this, so I'll do a pull request for it.