According to documentation for Apollo’s GraphQL-tools: You don’t need to specify resolvers for every type in your schema. If you don’t specify a resolver, GraphQL.js falls back to a default one… The documentation goes on to state that the default resolver will look for a property on the parent object with the field name that’s […]
JMeter is a load testing tool for a variety of network services. It supports features such as parameterization, assertions, cookies, and additional functionality through plug-ins.
In my last post, I described how you can build flexible APIs with GraphQL, using a family tree API as my demonstration. The implementation of the API was fairly simple, and I was able to traverse the graph of relationships between different people in the data set. In this post, I’ll demonstrate how we can […]
Over the past year, I’ve been working with GraphQL to build APIs. GraphQL is a query language that allows for flexible endpoints for servers, giving consumers the power to control what data they are receiving.
We’ve recently been using a combination of TypeScript, GraphQL, and React on a number of single-page app projects at Atomic. These technologies works extremely well together, but only after a significant investment in configuration, tooling, and ergonomics.
In my post about GraphQL and the Apollo server tools, I primarily focused on setting up a simple GraphQL schema and set of resolvers, but did not go much deeper. The main example in that post defined a findBy method which simulated hitting a database, but for the sake of brevity, this detail was largely […]