search

franzenzenhofer / f19n-obtrusive-livetest

A sandboxed, extendable testing chrome extension and framework! It runs pre-defined and custom tests on each page that you visit.
https://chrome.google.com/webstore/detail/f19n-obstrusive-live-test/jbnaibigcohjfefpfocphcjeliohhold?hl=en
55 stars 1 forks source link

catch error output for async rules #53

Closed franzenzenhofer closed 7 years ago

franzenzenhofer commented 7 years ago

hi @neuling

is there any way (or coding style in the async rules) to capture a failed rules similar as we do synchronous rules?

https://github.com/franzenzenhofer/f19n-livetest-chrome-extension/blob/master/src/javascripts/sandbox.js#L11-L13

with synchronous rules if a rule fails (which can happen) we see the error output in the panel

while with async we only see in the in the background.html developer console.

is there way to do this, or do we need to implement this in the async rules with a try/fetch

note: no going down the rabbit hole, this debugging behaviour is not MVP critical

franzenzenhofer commented 7 years ago

PRIO feature low

neuling commented 7 years ago

@franzenzenhofer is this still an issue?

franzenzenhofer commented 7 years ago

nope

On Fri, Apr 28, 2017 at 11:16 AM, Moritz Kobrna notifications@github.com wrote:

@franzenzenhofer https://github.com/franzenzenhofer is this still an issue?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/franzenzenhofer/f19n-livetest-chrome-extension/issues/53#issuecomment-297950099, or mute the thread https://github.com/notifications/unsubscribe-auth/AATudhiA8gbh-5ADoWduAXUuYMCuzLr8ks5r0a5hgaJpZM4Mdwkr .