I agree, that is a problem: people forget the ”graph” in GraphQL. It’s too easy to just create new query resolver to resolve that one ticket instead of thinking

I agree, that is a problem: people forget the ”graph” in GraphQL. It’s too easy to just create new query resolver to resolve that one ticket instead of thinking how data relates to other data and how it could be resolved using that other data. That is ultimately a people problem, however: why doesn’t it click that a ”resolver” is intended to ”resolve” other entities based on fields of the parent entity?