Allowing composite types

[Weakky]

Description

So far, nexus-prisma was working on the assumption that your prisma models would match your graphql type name. That limitation has already been removed, but we'd like to go one step further, by enabling the ability to "stitch" resolvers from several models.

Use-case

It might be that you have several users models (Customer, Admin, Moderator...), but that you'd like to expose them all as on single GraphQL object type.

Rough proposal

export const User = objectType({
  name: 'User',
  definition(t) {
    t.models.Customer.something()
    t.models.Admin.somethingElse()
    t.models.Moderator.somethingElseElse()
  }
})

Side notes

That is also be related to #302 as we'll need to handle backingTypes.

[jasonkuhrt]

Lets gather more use-cases. Feels like something that is powerful in concept but whose utility is highly coupled to situation/context. I'm lacking the imagination to think of such situations right now :)

I wonder if composites in practice would be more likely to mash disparate models together rather than your current example of closely related things put under a generalized type. Really not sure... 🤔