3 ms·
Everyone who is responding "well, the author just doesn't really understand REST", is pretty much correct, but I feel like they're ignoring the broader point of
by hn_throwaway_99 4y ago
Everyone who is responding "well, the author just doesn't really understand REST", is pretty much correct, but I feel like they're ignoring the broader point of practicality. I absolutely have seen the problem the author describes, not to mention other issues that come from the fact that using response codes in REST doesn't really separate "technical" problems from "business/domain" problems.
Just another reason I'm a big fan of GraphQL - error handling is much more clearly defined, with responses returning a 200 and the body defining the error.