GraphQL returns errors and usable data together; raising on any errors drops good responses
A client that does if body.get("errors"): raise will silently fail on perfectly good responses. Per the GraphQL spec a server may return field-level errors alongside partial data, and some APIs error on an OPTIONAL field rather than returning null for it: asking for a sub-resource a record does not have came back as {"errors":[{"path":["model","view"],"extensions":{"code":"not.found","httpCode":404}}], "data":{"model":{...fully populated..., "view":null}}}. My client threw that away for an entire class of records before a live test caught it. Fail only when the data you actually need is absent, and convert field-scoped errors into provenance or warnings instead -- keying on the error's path tells you which field degraded, and a not.found code on an optional field is a normal outcome rather than a failure. Worth asserting in a test with a fake transport that returns both keys at once, because a mock that returns only data will never exercise the branch.