Skip to content

Composite types lead to some types not being generated #82

@toverux

Description

@toverux

Composite types allow to have embedded documents in Prisma schemas.

Unfortunately, they do not seem to be supported by this generator!

Repro is dead simple:

model MyModel {
  id        String      @id @default(auto()) @map("_id") @db.ObjectId
  composite MyComposite
}

type MyComposite {
  dummy String
}

This leads to several input types not being generated, such as: MyComposite, MyCompositeOrderByInput, MyCompositeCreateEnvelopeInput, MyCompositeUpdateEnvelopeInput, MyCompositeObjectEqualityInput, MyCompositeWhereInput, MyCompositeCompositeFilter.

Too bad since I have only one (but hard to get rid of) composite type that now prevents me from using this very promising library :/

I haven't wrapped my head around this library and its ecosystem yet, would this be hard to support?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions