Automatic and model<>crud coordinating mapping API

[jasonkuhrt]

We currently have no hollistic mapping API. Users can, model-by-model write mappings. But these do not coordinate automatically in any way with the t.crud API. Users need to manually use the type and alias options. This is boring and error prone. When the user screws it up, they get confusing feedback giving them the wrong advice (e.g. "did you forget to export 'Person'?").

const Query = queryType({
  definition(t) {
    t.crud.user() // run time error
    // t.crud.user({ type: 'Person' }) // <-- fixes it
  },
})

const User = objectType({
  name: 'Person',
  definition(t) {
    t.model('User').id()
    t.model('User').email()
  },
})

type Person {
  email: String!
  id: Int!
}

type Query {
  user(where: UserWhereUniqueInput!): User # bug
}

type User {
  email: String!
  id: Int!
  post: Post
}

input UserWhereUniqueInput {
  email: String
  id: Int
}

[Weakky]

A couple of ideas:

Option 1

We could introduce a t.model.mapsTo('<prismaModelName>') function to avoid having to pass t.model('<prismaModelName>').field() on all calls.

Problems:

• That would probably break the TS magic we currently have (making the type property required when typeName doesn't map to any prisma model names)

Option 2

(Not sure if feasible)

If all t.model('<modelName>').field() uses the same modelName, then we could infer that typeName maps to modelName. This way it would not even go in the way of composite types if we ever support them (#298)

Problems:

• Same problem for type-safety though: I think there's no way to compute what's described above at compile time and dynamically make the type property required.