bad_request should also return an error code
Describe the bug
Every requests made that fails is returned a json response with a string field bad_request specifying the error.
For a client that needs to handle the failed requests it is not comfortable working with these strings.
It also can happen in the backend to change the string of a particular error, and if the client is checking for the previous string it will not catch it.
Expected behavior
Every bad_request should also include an int like error_code, for example like this:
{
"error_code": 10,
"bad_request": "The PGP signed cleartext message is not valid."
}
is this issue resolved @jerryfletcher21 and @KoalaSat ?
@KoalaSat I can work in this issue if you like
Ey @hexlorn that ks for pinging, it seems I missed @Sansh2356 's request. Let's wait for an answer, if not I'll assign it to you
Ey @hexlorn that ks for pinging, it seems I missed @Sansh2356 's request. Let's wait for an answer, if not I'll assign it to you
@KoalaSat you can assign it to @hexlorn i won't be able to do due to some health issue as of now.
Assigned to you @hexlorn thank you
@Sansh2356 I hope you get well soon 💪
@KoalaSat Since there has been no activity for the past 4 months, I assumed this issue was available to take. I opened a pull request to fix this. Could you assign me?