cm0002@lemmy.world to Programmer Humor@programming.dev · 4 months agoYes, But...lemmy.mlimagemessage-square58fedilinkarrow-up1407arrow-down14cross-posted to: [email protected]
arrow-up1403arrow-down1imageYes, But...lemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 4 months agomessage-square58fedilinkcross-posted to: [email protected]
minus-squaremadcaesar@lemmy.worldlinkfedilinkarrow-up0·4 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-up1·4 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?