Comment #40 on issue 3093 by [email protected]: Debugging promises
http://code.google.com/p/v8/issues/detail?id=3093
Unlogging just sounds like a bad user experience to me. If you have the
console open you'd see the error flicker by.
But, even that aside, a pure-devtools based solution is insufficient. It's
a deal-breaker if apps need to add rejection handlers to all their promises
in order to be able to capture JS errors to log back to the server.
window.onerror needs to work by default. The window.onerror-breaking mode
needs to be opt-in.
> The use-case of explicitly wanting to add rejections after the fact
seems really niche to me.
Let me assure you that, having written many, many promise-using
applications, it is not niche and shows up in any nontrivial asynchronous
code.
Depends on your definition of niche I suppose. I think it's *much* less
common than wanting to get errors messages when you typo.
What are you suggesting as the solution? Do you think having the devtools
break on exception thing work better is actually sufficient? I don't.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
