Is there an accepted pattern to building a graphql mutation where the resolver would essentially boil down to [an existing resolver] + [another existing resolver]?
As in,