Keep bounded data type? about angular-material-datetimepicker HOT 6 CLOSED

@j-walker23 you are right. Easiest way to check: {{date._isAMomentObject}}

._d is the internal date of moment.

$mdDialog.show(dialogOptions).then(function(v) {
   scope.currentDate = v ? v._d : v;

Do you know why ?

from angular-material-datetimepicker.

from angular-material-datetimepicker.

Actually, i think i might have a feature request after looking at the code. If i pass a moment utc value in, then the object returned after date/time selection stay in utc.

This came up from giving the directive a utc moment object. Then after an edit through the directive is made, the date shown gets shifted by whatever my timezone offset is. Confusing the user who selected a time, and then is displayed what might seem like a different random time. Guessing that would be new functionality.

I can handle conversions with ng-change. Just thought i would bring it up. Thanks again.

from angular-material-datetimepicker.

@j-walker23 can you test it?

Yes it's a bug and can be confusing.
Now if a moment utc is passed it will stay as passed.
Do not use with edit-input="true" for now.

Since version 1.0, logbon72 chose to return a js date, but returning a moment (local) can also be done.

from angular-material-datetimepicker.

Damn, i just saw this. Thank you, I will test it today!

from angular-material-datetimepicker.

Worked perfectly. Thank you!

from angular-material-datetimepicker.