types: make MockResolver recursive with ResolverMap

[derrh]

In projects with strict prohibitions against inferred any types, resolver maps that include Query or Mutation resolvers will result in type errors unless they are explicitly typed.

The following code results in a TypeScript error if you do not manually specify params and return types for the resolver

  mocks: {
    Query: () => ({
      user: (_parent, args) => ({
        userId: args.userId,
      }),
    }),
  }

Error:

[donovanhiland]

@derrh I think this is a bigger problem than just with Query and Mutation types. If you access resolver arguments in any inline resolver this will happen. It's kind of a verbose problem to solve because the type-system needs to be aware of the entire schema to provide accurate types.

I plan on looking into a way to type the mocker based on the user's schema but for now maybe you can just pass _parent: any explicitly to make typescript happy?

[donovanhiland]

🎉 This PR is included in version 1.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀