Fork me on GitHub
#graphql
<
2019-04-29
>
donaldball20:04:55

Do folk have error response patterns they’re finding particularly helpful or painful? I’m thinking here of the ways in particular a mutation could fail: 1. invalid parameter values 2. unauthorized 3. storage error I tend to think the least wrong thing would be to adopt the principle that every mutation may return a failure response of a consistent shape, and that that’s entirely distinct from the top-level errors key of the whole graphql response, which seems oriented towards expressing syntactical or grammatical problems with requests. This is all speculative though, I’d appreciate observations based on real-world experience.