bug: Angular 1.x App with Zone.js about zone.js HOT 11 CLOSED

+1

from zone.js.

Please provide a reproduction via plnkr.co, jsfiddle, or [jsbin(http://jsbin.com/). This saves me a lot of time. Thanks!

from zone.js.

fixed my link.. sorry guys.
http://plnkr.co/edit/pm5yrJ?p=info

from zone.js.

I have a problem using long-stack-trace-zone.js with angular too. When I use angulars $timeout its not possible to get a stack trace. Using setTimeout works perfectly fine. Same issue using $promise.

http://plnkr.co/edit/OvExnTzRQaSGv45evxHv

from zone.js.

Looking into it. Thanks for the reproductions.

from zone.js.

Any updates on using zone.js in this way with angular 1.4?

from zone.js.

Pretty sure this is because angular's $exceptionHandler eats uncaught exceptions inside $apply'd functions/expressions and logs them to the console. This means they will never reach zone.

In my angular 1.x app that I'm using with zone, I'm decorating $exceptionHandler to rethrow errors.

See https://docs.angularjs.org/api/ng/service/$exceptionHandler

from zone.js.

Thanks! Would you mind sharing an example of how you are doing the decoration?

Sent from my iPhone

On Sep 9, 2015, at 9:12 AM, Matthew Hill <[email protected]mailto:[email protected]> wrote:

Pretty sure this is because angular's $exceptionHandler eats uncaught exceptions inside $apply'd functions/expressions and logs them to the console. This means they will never reach zone.

In my Angular 1.x app that I'm using with zone, I'm decorating $exceptionHandler to rethrow errors.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/29#issuecomment-138959706.

from zone.js.

Sure. Off the top of my head:

module.config(function($provide) {
  $provide.decorator('$exceptionHandler', function($exceptionHandler) {
       return function(error, cause) {
            $exceptionHandler(error, cause);
            throw error;
       };
   });
});

from zone.js.

Thank you sir! :)

Sent from my iPhone

On Sep 9, 2015, at 9:33 AM, Matthew Hill <[email protected]mailto:[email protected]> wrote:

Sure. Off the top of my head:

module.config(function($provide) {
$provide.decorator('$exceptionHandler', function($exceptionHandler) {
return function(error, cause) {
$exceptionHandler(error, cause);
throw error;
};
});
});

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/29#issuecomment-138965024.

from zone.js.

Why hasn't this been addressed? I'm currently using zone.js 0.5.15 (outdated) to be able to use Fetch API instead of $http in my Angular 1.x app but trigger the digest cycle after multiple asynchronous operations. I haven't been successful using the new API, so I would like some guidance.

What I'm doing is the following:

// Zone addon, so it wraps the promise chain in one "zone" and
// executes some arbitrary task (in this case rootScope digest run)
// after the promise chain.

const scopePrototype = $rootScope.constructor.prototype;
const originalApply = scopePrototype.$apply;
const zoneOptions = {
    afterTask: function afterTask() {
        try {
            $rootScope.$digest();
        } catch (e) {
            $exceptionHandler(e);
            throw e;
        }
    }
};

scopePrototype.$apply = function $applyFn() : void {
    // tslint:disable-next-line:no-var-self
    const scope = this;
    const applyArgs = arguments;

    window.zone.fork(zoneOptions).run(() => {
        console.log('Running zone');
        originalApply.apply(scope, applyArgs);
    });
};

from zone.js.