Default error handling on resources.

[jonabrams]

Default error handling on resources.

[JonAbrams]

Excellent suggestion! It could even handle the error differently depending on if it's running in production mode or not.

[mikaelhm]

👍 Yes, that was my point :)

[sylg]

👍

[JonAbrams]

I love that by using promises, we can now safely throw errors right in the request handler! 😃

[mikaelhm]

Yes, it's really nice! 👍

[JonAbrams]

Thanks! I don't think I'm quite done with it yet. At some point I'd like to add some more flexibility, like register a subscriber for errors, so you can hook in services like Airbrake. Also, some errors probably don't need to be suppressed in production. Maybe add a {… public: true } attribute to tell the error handler that it's ok to share the response with the client?

[mikaelhm]

Sounds good, I would love to use Opbeat. But that shouldn't be too hard with opbeat-node.

Regarding the "public" errors, I think thats a brilliant idea! That would make it very simple to do proper error messaging "right at the spot".