You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
422/same code as validation errors. In case all request validation is updated from 400 to 422 we still want the error message to be informative about masks format (only start, end) rather than referring to "trailing characters" which is less intuitive
Error can look like the case of "masks": [[0, 6]] which returns {"code":422,"details":"invalid masks"}
Observed behavior
{"code":400,"details":"Failed to parse the request body as JSON...
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently while most validation errors return
422
, failing masks validation on the classification endpoints returns400
with an error likeSample Code
Example call
Expected behavior
422
/same code as validation errors. In case all request validation is updated from400
to422
we still want the error message to be informative aboutmasks
format (only start, end) rather than referring to "trailing characters" which is less intuitiveError can look like the case of
"masks": [[0, 6]]
which returns{"code":422,"details":"invalid masks"}
Observed behavior
{"code":400,"details":"Failed to parse the request body as JSON...
The text was updated successfully, but these errors were encountered: