Could be worse. My DND character is in a precarious spot until next week and has a chance it could do very poorly.
I’ve also only had meetings at work today and I’m hiding under a blanket on my couch before this next meeting in 1 minute.
Looking forward to getting some better sleep and getting some gaming in later.
I like the fourth or the last one since it encourages all other error responses to follow a similar standard. That will allow the client to have a reusable error model and error checking.
I’ve had to use APIs where every response was 200 ok with json, 400 bad request with pain text that said unauthorized, or a 500 error that returned an HTML error page. The worst.