2 ms·
Expressive error messages are great. Calling errors a "success" is wrong. Check out my slides here for more: https://speakerdeck.com/caseysoftware/12-reasons-y
by caseysoftware 9y ago
Expressive error messages are great. Calling errors a "success" is wrong.
Check out my slides here for more:
https://speakerdeck.com/caseysoftware/12-reasons-your-api-sucks-2017-rev https://speakerdeck.com/caseysoftware/12-reasons-your-api-su...
Slides 38-40 are specifically about expressive and useful error messages.
- grandalf 9y agoYour slides illustrate a custom response payload which happens to use codes that numerically match HTTP status codes. You also use a response message, I think we actually agree. I'd recommend using a different numerical namespace to avoid any possible confusion about the semantics of those codes. Just because they sound the same to one person reading the spec doesn't mean they will make sense to others.
- caseysoftware 9y agoUnderstood on that point. The response codes are in those payloads purely for illustrative purposes.