Closed anthonyroach closed 2 years ago
Thanks for reporting! Would you like to send a Pull Request to address this issue? Remember to add unit tests.
Certainly!
@jonnydgreen thanks for the quick turn around on the PR merge and 3.0.0 release. I verified the fix for this issue in my project and it works as expected:
HTTP/1.1 400 Bad Request
cache-control: no-cache
content-type: application/json; charset=utf-8
content-length: 562
Date: Tue, 05 Jul 2022 15:02:52 GMT
Connection: close
fantastic, thanks for verifying and no problem at all :)
Validation errors mean the client sent something invalid, so they should result in a 400 status code but instead they result in a 500 status code.
Library versions:
Example: