Yeah, we were discussing better error messages today, so that instead of the application acting like that it would know what went wrong and show the right message.
So far our API errors are based on HTTP error codes... and that one is 400 bad request.
It's a bad request as the username is taken... but really that shouldn't freak out, it should return the 400 bad request and additional info so that the app could know why and then handle it elegantly "That username is taken, but how about this one...".
Yeah, we were discussing better error messages today, so that instead of the application acting like that it would know what went wrong and show the right message.
So far our API errors are based on HTTP error codes... and that one is 400 bad request.
It's a bad request as the username is taken... but really that shouldn't freak out, it should return the 400 bad request and additional info so that the app could know why and then handle it elegantly "That username is taken, but how about this one...".