search

daluu / Extendables

My fork of the (test) framework for Adobe ExtendScript
http://debrouwere.github.com/Extendables/
MIT License
2 stars 0 forks source link

Try catch blocks fail when Extendables included #2

Open daluu opened 9 years ago

daluu commented 9 years ago

Logging for tracking purposes, since original Extendables project this fork is from has no issue tracker. To reproduce, run this snippet in any Adobe app or ExtendScript toolkit.

#include "pathTo/Extendables/extendables.jsx";
try{
    throw Error("intentional failure");
}catch(e){
    alert("caught: "+e.message);
}finally{
    alert("cleanup");
}

Without Extendables, we see the alerts as appropriate. With Extendables, executing the code brings up ExtendToolkit in debug mode stuck/stopping at the line where error is thrown.

Need to look into what within Extendables causes this.

daluu commented 9 years ago

Thought that this commit below may have helped but doesn't appear so:

https://github.com/abe33/Extendables/commit/0c0ac84d9b0be08212022015afc1efd472255bd3

daluu commented 9 years ago

FYI, this issue was found earlier in a Adobe forum post: https://forums.adobe.com/thread/998305?sr=stream

I've only encountered it recently as just started using Extendables.

daluu commented 9 years ago

FYI, tested on Adobe (Illustrator) CS6.

daluu commented 9 years ago

Per Stijn, the original framework developer:

It might have something to do with the extensions to Error in patches/error.jsx?

also to check core-packages/utils/lib/error.jsx

I tried just using blank files, not extending Error and that seemed to do nothing.

daluu commented 9 years ago

Is, in a way, fixed in the "unextendables" branch of this project, as long as you selectively choose not to import the Error module, say importing only the core base modules and anything else (e.g. testing, logging, templating, using runner.unextended.framework.jsx).