I AM GOING TO PERSONALLY MURDER WHICHEVER SHITBRAINED INCOMPETENT MONKEY THOUGHT IT'D BE A GOOD IDEA TO RESPOND TO ANY AND ALL API ERRORS BY SENDING A RESPONSE WITH THE STATUS CODE 200 AND A BODY OF THE FUCKING STRING "error" AND NOTHING ELSE

WHY?!!?!?!??!

Sorry about that. I just wanted to hear you scream.

@AlmondSauce Their screaming gets you off, doesn't it?

*sniff* Despair. Anger. Sadness.

Violence is in the air...

Not to motivate you, but Home Depot has quite an ordeal of 5$ appliances that might be very useful.

*smiles with an approving nod*

Ah, classic :)

I had a similar experience recently. It was "null" instead of "error".

Aha. Server code generated by swagger can do this before you finish stubbing it out. I recently ran into this as the developer :)

Client-side app developers were a little over-eager and started testing features I hadn't marked as complete yet, and complained that "well, everything is working (code 200), but I'm getting an empty response!"

"Well, if the response is empty, it doesn't match the spec. If it doesn't match the spec, file a bug."

Bug gets filled. Reporting on features I'm not set to deliver for another 2 weeks. SMH

Easy phonecall to clear up, but it's not fun to waste time 🙂

I have worked with phyton/java/node/php BE devs, they all do this.. Funniest thing was that Java ones sent the worst codws or none at all, and PHP guys did the best job.

Recently had a server responding with 200, regardless of the actual http code. Instead, the correct status code was send in the body 🤷‍♂️ That were some hours I will never get back...