cm0002@lemmy.world to Programmer Humor@programming.dev · 13 days agoYes, But...lemmy.mlimagemessage-square46fedilinkarrow-up1674arrow-down18
arrow-up1666arrow-down1imageYes, But...lemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 13 days agomessage-square46fedilink
minus-squaremadcaesar@lemmy.worldlinkfedilinkarrow-up13arrow-down2·12 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-up19·12 days agoWhat about both? User supplies bad input? HTTP 400 with response body json describing the error in a standard format?
minus-squarebountygiver [any]@lemmy.mllinkfedilinkEnglisharrow-up6·12 days agowhen you are too lazy to ask your request library to not throw exception on non-200 responses.
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?
when you are too lazy to ask your request library to not throw exception on non-200 responses.