Resolvers best practices?

Hi Ben,

I'm working on a [project](https://github.com/timthedev07/your-doge), where I have a single giant user resolver class with the `@Resolver()` decorator. And recently I'm starting to wonder if it is actually better to split them up into separate files and use a utility function to manually import each resolver from each individual file. But I guess there is a tradeoff, that is, every time I create a new resolver, I need to go back to that utility function to import it from the newly created file, and in fact, I'm going to create many other resolvers in the future.

[UserResolvers.ts](https://github.com/timthedev07/Your-Doge/blob/staging/shibe/src/resolvers/UserResolvers.ts)

I would appreciate your suggestions on what to do in this case.

Start by reading the linked UserResolvers.ts file and the resolver organization described in the issue. Compare the current structure with the project's existing resolver entry points, but note that the issue provides no requested change or acceptance criteria, so there is no defined completion state.

Written by the indexing model from the issue text.