$q.reject() returns a promise with then() but no catch() and no finally()

[wesleyakio]

When creating a rejected promise with $q.reject(reason) the resulting promise does not have the catch and finally methods.

[wesleyakio]

Currently overriding $q.reject in a decorator, a little bit annoying since the decorator must go into every single module that depends on catch and finally from the reject sugar...

$provide.decorator('$q', function($delegate) {
  $delegate.reject = function(reason){
    var deferred = $delegate.defer();
    deferred.reject(reason);
    return deferred.promise;
  };
  return $delegate;
});

The "light" promise returned from $q.reject should perform better, but returning a "real" rejected promise might make things easier when extending the promise itself.

[lgalfaso]

#5976 should be able to handle this

[wesleyakio]

Looking at the pull request it does seem to handle it.

Will the path to compliance eventually lead angular to drop support for catch and finally?

[IgorMinar]

we should fix this in 1.2 (#5976 can't go into 1.2)

[lgalfaso]

@IgorMinar you are right, will create a new PR just for this fix