Better error handling for humans about express-stormpath HOT 8 CLOSED

I actually just started making changes to correct this in the last 2 releases -- I currently re-did the password reset stuff to work properly on edge cases like this, and will roll out the rest of those changes for the other endpoints.

Sorry about that!

When I initially wrote this I skimped on the error handling there ><

from express-stormpath.

Awesome! Do you have an idea of when it could be released? Just want to know if I do a quick patch on my end while I wait for the official support for this (no pressure).

from express-stormpath.

I am prolly gonna get to this one tomorrow! So, if you need it before then you can hack it together ^^

from express-stormpath.

Tomorrow is alright ☺
On Oct 27, 2014 5:51 PM, "Randall Degges" [email protected] wrote:

I am prolly gonna get to this one tomorrow! So, if you need it before then
you can hack it together ^^

—
Reply to this email directly or view it on GitHub
#28 (comment)
.

from express-stormpath.

Quick update: working on this now.

from express-stormpath.

Bump this - a lot of useful error information (such as when an account store is disabled) is simply being rendered as an "Oops" message

from express-stormpath.

OK. I have an idea for this.

I'm thinking about creating an event emitter for error handling.

EG:

app.on('failedAPIAuthenticationAttempt', function(req, res, next) {
...
});

app.on('failedWebAuthenticationAttempt', function(req, res, next) {
...
});

etc

What do you think?

from express-stormpath.

This was fixed a long time ago, the library is now directly passing errors that come from the Stormpath API.

from express-stormpath.