Lean in to the graph when writing resolvers

Designing great resolver functions in GraphQL is quite unintuitive. Giving consumers the ability to describe their desired response payload means it’s possible for consumers to access fields via surprising paths through the graph, and this is something that can and should influence how you write your resolvers on a field level. Say you’re building a kanban board app like Trello or Asana. A board…