Change event is sometime fired unnecessarily about angular-moment-picker HOT 2 CLOSED

Hi @vedard, sorry for the late response.
Well, because of how Angular works, every time in the first $digest cycle it fires all $watch callbacks. You can check out this behavior in this simple plunker.

Anyway that's not a really big problem, you can just check if the newValue is defined and is different from the oldValue:

$scope.onChange = function (newValue, oldValue) {
    if (!angular.isDefined(newValue) || angular.equals(newValue, oldValue)) return;
    // perform your stuff...
};

from angular-moment-picker.

Hi @vedard, your problem will be solved (by design) in the next major release of the directive.
It will have a big breaking change (it will work with Moment Object instead of formatted moment strings) and if you are interested in it, you can have a look at #60 (comment).

Anyway, I'm going to close this issue. Feel free to open it again if you'll still have any trouble.
Thanks :)

from angular-moment-picker.