cm0002@lemmy.world to Programmer Humor@programming.dev · 14 days agoYes, But...lemmy.mlimagemessage-square76fedilinkarrow-up1732arrow-down19
arrow-up1723arrow-down1imageYes, But...lemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 14 days agomessage-square76fedilink
minus-squaremadcaesar@lemmy.worldlinkfedilinkarrow-up12arrow-down2·14 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-up21·14 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?