cm0002@lemmy.world to Programmer Humor@programming.dev · 3 months agoYes, But...imagemessage-square23fedilinkarrow-up192
arrow-up192imageYes, But...cm0002@lemmy.world to Programmer Humor@programming.dev · 3 months agomessage-square23fedilink
minus-squaremadcaesar@lemmy.worldlinkfedilinkarrow-up2·3 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-squarefuzzzerd@programming.devlinkfedilinkEnglisharrow-up3·3 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?