Return 400 instead of 500/404?

[mmoravcik]

Any reason why the app return 500/404 error instead of 400 in these, and perhaps other, cases?

• non-existent email address has been provided
• token is invalid (expired, deleted, mistyped)

I think that catching 400 and getting the errors from the response would be much neater to work with in FE?

[anx-ckreuzberger]

I have always "caught" that behaviour in a custom exception handler of django rest framework, but I'll take a look at what can be done within the package.

edit: But it should never return a 500 anyway :)

[anx-ckreuzberger]

I've created issue #19 for this and closing this one.

[anx-ckreuzberger]

Changes for this have just released in Version 1.0.0a1.