8 replies

Explicitly specifying an object in Prisma with its foreign relationships

I've set up my schema as an approximation of a directory structure: directories (

ADir

ADir

s) and documents (

ADoc

ADoc

s). Directories and documents can have a parent directory, which is a foreign key.

I can write queries to retrieve directories and their children (

childDirs

childDirs

childDocs

childDocs

) without issue, but if I specify a directory as a state variable in a client component with

useState

useState

, the type definition for

ADir

ADir

that I get from importing

@prisma/client

@prisma/client

does not have the children as a property.

I've circumvented this issue by extending the type with my own interface, but I feel like it's a messy fix. Any tips? Thanks.

// helper for ADir object types that also need their children
// TODO: is there a better way to specify foreign objects in a type?
export interface ADirWithChilren extends ADir {
  childDirs: ADir[],
  childDocs: ADoc[]
}

// helper for ADir object types that also need their children
// TODO: is there a better way to specify foreign objects in a type?
export interface ADirWithChilren extends ADir {
  childDirs: ADir[],
  childDocs: ADoc[]
}

further reference: related libs are just next (using app router) and prisma. No trpc, zod, or superjson packages, but not against them if they are key to a good implementation.

Solution

so then I'd get a type like this

export type Dir = Awaited<ReturnType<typeof getDir>>[number];

export type Dir = Awaited<ReturnType<typeof getDir>>[number];

Jump to solution

TTC

Theo's Typesafe Cult•3y ago•

8 replies

dumbitry

Explicitly specifying an object in Prisma with its foreign relationships

I've set up my schema as an approximation of a directory structure: directories (

ADir

ADir

s) and documents (

ADoc

ADoc

s). Directories and documents can have a parent directory, which is a foreign key.

I can write queries to retrieve directories and their children (

childDirs

childDirs

childDocs

childDocs

) without issue, but if I specify a directory as a state variable in a client component with

useState

useState

, the type definition for

ADir

ADir

that I get from importing

@prisma/client

@prisma/client

does not have the children as a property.

I've circumvented this issue by extending the type with my own interface, but I feel like it's a messy fix. Any tips? Thanks.

// helper for ADir object types that also need their children
// TODO: is there a better way to specify foreign objects in a type?
export interface ADirWithChilren extends ADir {
  childDirs: ADir[],
  childDocs: ADoc[]
}

// helper for ADir object types that also need their children
// TODO: is there a better way to specify foreign objects in a type?
export interface ADirWithChilren extends ADir {
  childDirs: ADir[],
  childDocs: ADoc[]
}

further reference: related libs are just next (using app router) and prisma. No trpc, zod, or superjson packages, but not against them if they are key to a good implementation.

Solution

so then I'd get a type like this

export type Dir = Awaited<ReturnType<typeof getDir>>[number];

export type Dir = Awaited<ReturnType<typeof getDir>>[number];

Jump to solution

Explicitly specifying an object in Prisma with its foreign relationships

Similar Threads

Explicitly specifying an object in Prisma with its foreign relationships

Similar Threads

Similar Threads

Similar Threads