Using Mongo DbObject Types in Resolvers

[tubbo]

We're using the following plugins:

      - 'typescript'
      - 'typescript-document-nodes'
      - 'typescript-mongodb'
      # depends on mongo types and must come after them
      - 'typescript-resolvers'

Our GraphQL schema has a lot of types that look something like this:

interface Product @abstractEntity(discriminatorField: 'someField') {
  id: ObjectID! @id
  someField: String! @column
}

type SomeProduct implements Product @entity {
  id: ObjectID! @id
  someField: String! @column
  # ...my kingdom for schema fragments...
  relationToSomethingElse: SomethingElse! @link
}

Because of that @link field, we need to be able to resolve that type in such a way that the parent type passed into the resolver is not the same type that the resolver will eventually hand back to the client. So we've been adding mappers to our codegen.yml:

config:
  mappers:
    Product: ProductDbObject
    SomeProduct: SomeProductDbObject

This allows us to write a resolver like so:

export const SomeProduct: Partial<SomeProductResolvers> = {
  relationToSomethingElse: async ({ relationToSomethingElse }, _, { dataSources }) => await dataSources.somethingElse.getSomethingElse(relationToSomethingElse)
}

This is all fine right now, but it seems to be a lot of boilerplate code just to get interfaces and implementing types to resolve properly, and furthermore be able to define things like relations or "virtual" fields that aren't backed by a database. As such, we feel that we're going to have a lot of types that end up this way, so we were looking to do this in a slightly more sustainable way. Is there any way to basically "default" the resolvers types to use *DbObject types generated by typescript-mongodb?