cm0002@lemmy.world to Programmer Humor@programming.dev · 10 days agoYes, But...imagemessage-square24fedilinkarrow-up192
arrow-up192imageYes, But...cm0002@lemmy.world to Programmer Humor@programming.dev · 10 days agomessage-square24fedilink
minus-squaremadcaesar@lemmy.worldlinkfedilinkarrow-up2·10 days 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·10 days 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?