Relationships: Polymorphic Types

model report {
    id String @id
    message String
   reportable @morphRelation(models: [User, Post])
}

model User {
  id String @id
  name String
}

model Post {
  id String @id
  content String
}

When adding a “morph map” to your existing application, every morphable *_type column value in your database that still contains a fully-qualified class will need to be converted to its “map” name.

reference👉https://laravel.com/docs/8.x/eloquent-relationships#custom-polymorphic-types

[laugharn]

I think a common use case for this would be something like an activity feed. Imagine a platform-like site where people can post, comment, like, etc. It would be nice to have a model like:

model Activity {
  id String @id
  model @morphRelation(models: [Comment, Like, Post])
}

And in the client, we would be able to make a request like prisma.activity.findMany({ include: { model: true }}) and get the Comment, Like, or Post back with each Activity, without having to specify all of the possible relations everywhere an Activity will be called.

[pantharshit00]

Ok, actually found the duplicate issue for this: https://github.com/prisma/prisma/issues/2505

I knew it existed. Sorry for linking the interface one at first.

Add your proposal and +1 to that issue.