Make ngClick only $apply when it doesn't return a promise

[pocesar]

ngClick should not ignore the return value of the underlaying function. Check if it's a promise, then don't call an unnecessary $scope.$apply, since it will be resolved and applied when $q resolves.

My case: I use a third party promise library bluebird, and do a lot of UI display calculations (prices and discounts) before displaying on the UI. Currently there's a flicker on the UI because the model is emptied (while the ngClick happened) and recalculated through the bluebird promise, that is wrapped using $q.when (that also calls a second $apply when it's resolved), since it's called on the next cycle.

[IgorMinar]

I don't think that this has anything to do with ngClick. Rather, the Scope#$evalAsync should make it possible to schedule $q next tick via microtasks.

[IgorMinar]

edited the subject. original was: "Make ngClick only $apply when it doesn't return a promise"

[pocesar]

because clickHandler is wrapped inside scope.$apply (in

angular.js/src/ngTouch/directive/ngClick.js

Line 277 in 36831ec

element.on('click', function(event, touchend) {

)

basically this:

    element.on('click', function(event, touchend) {
      scope.$apply(function() {
        clickHandler(scope, {$event: (touchend || event)});
      });
    });

would become

    element.on('click', function(event, touchend) {
      var ret = clickHandler(scope, {$event: (touchend || event)});
      if (ret && angular.isFunction(ret.then)) {
        ret.then(scope.$digest.bind(scope)); // then should $digest only if it's a non-trusted promise (other than $q)
      } else {
        scope.$digest();
      } 
    });

(of course I'm over simplifying the issue)

bluebird by default (and as per spec) call the promise on the next tick always, for a clean stack trace. $evalAsync wouldn't make a difference in this case.

[jeffbcross]

@IgorMinar did you mean to edit the subject? The current subject matches what your edit says the original was.

[lgalfaso]

I do not understand this request. Why a function that is called inside ngClick/$eval/$evalAsync cannot have side-effects that should be propagated immediately and return a promise?

[shahata]

@lgalfaso the promise thing is just a confusing implementation detail (which is not even necessary for the implementation). This issue is simply about the fact that the function inside ngClick or any other event handler might not have immediate side effects and therefore it would like to somehow skip the unnecessary digest. See the suggested PR (#8301) for more details...

[lgalfaso]

#8301 looks like an overkill If we only want to tackle this case. We should
just have new directives that eval the expression outside an $apply