From graphql.orgThis post is the first part of a series of best practices and observations we have made while building GraphQL APIs at PayPal. In upcoming posts, we’ll share our thoughts on: schema design, error handling, production visibility, optimizing client-side integrations and tooling for teams. You might have seen our previous post “GraphQL: A success story for PayPal Checkout” about PayPa
![GraphQL Resolvers: Best Practices](https://cdn-ak-scissors.b.st-hatena.com/image/square/31e29136af42249b086f0572387ad92a998e8535/height=288;version=1;width=512/https%3A%2F%2Fmiro.medium.com%2Fv2%2Fresize%3Afit%3A338%2F1%2AfMLqM5yV0HUWBGGYK7beLw.png)