Handling Errors Consistently
One shape for every error response, wherever it comes from.
An API that returns a stack trace to the client on one endpoint and a bare 500 on another has not been designed, it has accumulated. This topic is making every error response — however it was triggered — come out the same shape: a real exception type, a handler that knows what to do with it, and a body a client can actually parse and act on.
Contents
7 cardsnot started