@[email protected] to Programmer [email protected] • 7 days agoYes, But...lemmy.mlimagemessage-square84fedilinkarrow-up1730arrow-down19cross-posted to: [email protected]
arrow-up1721arrow-down1imageYes, But...lemmy.ml@[email protected] to Programmer [email protected] • 7 days agomessage-square84fedilinkcross-posted to: [email protected]
minus-square@[email protected]linkfedilink12•6 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-square@[email protected]linkfedilinkEnglish20•6 days agoWhat about both? User supplies bad input? HTTP 400 with response body json describing the error in a standard format?
minus-squarebountygiver [any]linkfedilinkEnglish7•6 days agowhen you are too lazy to ask your request library to not throw exception on non-200 responses.
minus-square@[email protected]linkfedilink5•6 days agoThrowing exceptions is fine since errors are an exceptional circumstance (not expected during normal use of the app), and you probably want errors to follow a different code path so that they can be logged, alerts triggered if needed, etc.
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.
Throwing exceptions is fine since errors are an exceptional circumstance (not expected during normal use of the app), and you probably want errors to follow a different code path so that they can be logged, alerts triggered if needed, etc.