@cm0002@lemmy.world to Programmer Humor@programming.dev • 2 months agoYes, But...lemmy.mlimagemessage-square38fedilinkarrow-up160arrow-down10cross-posted to: programmerhumor@lemmy.ml
arrow-up160arrow-down1imageYes, But...lemmy.ml@cm0002@lemmy.world to Programmer Humor@programming.dev • 2 months agomessage-square38fedilinkcross-posted to: programmerhumor@lemmy.ml
minus-square@madcaesar@lemmy.worldlinkfedilink0•2 months agoHere I am preferring 200, with success boolean / message string… Iike HTTP errors codes for real fuck up’s, if I see 500 somethings fucked in the app, otherwise a standardised json response body seems way easier
minus-square@fuzzzerd@programming.devlinkfedilinkEnglish1•2 months agoWhat about both? User supplies bad input? HTTP 400 with response body json describing the error in a standard format?
Here I am preferring 200, with success boolean / message string…
Iike HTTP errors codes for real fuck up’s, if I see 500 somethings fucked in the app, otherwise a standardised json response body seems way easier
What about both? User supplies bad input? HTTP 400 with response body json describing the error in a standard format?