Right now, most errors are labeled as internal server errors with their HTTP code, which isn't very accurate. To deal with this nicely, it would probably to define my own error type that includes both an error message and a HTTP status code, since the can't only be dealt with at the API level.
Right now, most errors are labeled as internal server errors with their HTTP code, which isn't very accurate. To deal with this nicely, it would probably to define my own error type that includes both an error message and a HTTP status code, since the can't only be dealt with at the API level.