configurable error handling
See original GitHub issueIs it possible to turn try { ... } catch
off in the bluebird promise implementation ?
It would be nice if we could opt out of having the then
handler wrapped in a try catch.
This would enable people to make different decisions about error handling opinions instead of going with the “defaults” promises/A+ choose.
Issue Analytics
- State:
- Created 10 years ago
- Comments:30 (7 by maintainers)
Top Results From Across the Web
Error Handling - OWASP Cheat Sheet Series
The article shows how to configure a global error handler as part of your application's runtime configuration. In some cases, it may be...
Read more >Error Handlers | MuleSoft Documentation
From Studio, drag an Error Handler component from the Mule Palette to the canvas, and configure it components through the UI. · In...
Read more >Error Handling Configuration Properties - IBM
Table 1 shows the configuration properties for error messages. For additional information on configuring the error handling, see Errors Sending Responses .
Read more >Chapter 9. Error Handling Configuration - JBoss.org
If an error occurs, the request control-flow changes according to the configuration. This configuration is known as the control policy. 9.2.1. Policy Delegation ......
Read more >Handle errors in ASP.NET Core | Microsoft Learn
To configure a custom error handling page for the Production environment, call UseExceptionHandler. This exception handling middleware:.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@wprater Its here - https://github.com/spion/promise-streams - but these dayse I recommend looking at reimplementations of node streams (instead of extensions like promise-streams). Node streams are too broken and quirky to fix.