API error responses are, in general, poorly documented. While in most cases we do not want to let on to the true underlying resource a request failed, that doesn't really apply to 400 cases. The Http Bad Request error is usually a failure in the client, and we'd like to at least provide hints as to how a request should be structured. Any place we throw an 400, we should include a helpful message.
API error responses are, in general, poorly documented. While in most cases we do not want to let on to the true underlying resource a request failed, that doesn't really apply to 400 cases. The Http Bad Request error is usually a failure in the client, and we'd like to at least provide hints as to how a request should be structured. Any place we throw an 400, we should include a helpful message.
Reference from #428