Valid, but dumb.
good old 418, always appears when you really want a cup of coffee
Why even use HTTP, when you can just send bytes directly over the physical network card, right?
Because standards make it better for everyone. You've no idea when, who or in what context the error will happen or be received by.
It takes so little to return ProblemDetails, and improves the experience of devs using your API so much. Just do it. Stop thinking up edge cases and faffing about with excuses. Do it.
Please, please, please, PLEASE return error-codes and problem-details.
Here's the RFC: https://www.rfc-editor.org/rfc/rfc9457.html
Then just return a 500 - Server error. Nice and obscure.
The ability to separate "something wrong with what you sent" (4XX) and "something wrong on the server" (5XX) is very valuable in itself.
As long as people keep giving them money they will keep pushing deadlines.
When people stop they will stop making and running the game.
A strange game, the only winning move is not to play.
Only if it's a cow
This is the way.
I don't validate emails, I test them.
That's your email? OK, what did we send it? if we couldn't send to it or the user can't read it there's no reason to accept it.
OK, maybe I do some light validation first, but I don't trust the email address just because it's email-address-shaped.
The day the nazi died - chumbawamba
And every one of those is delicious. I wonder what the originator tastes like.
vscode with edamagit and the cli