Wasp•10mo ago•

9 replies

Best way to generate null form values for a Prisma update

Not sure best place to ask this question, but I figure developers building CRUD forms in wasp might have the same question.

I have an entity like this:

model Foo {
  id String @id @default(uuid(7))
  bar String? 
}

model Foo {
  id String @id @default(uuid(7))
  bar String? 
}

I'm updating the entity like this in the back-end:

export const updateFoo: UpdateFoo<{
  id: string;
  bar?: string;
}, Foo> = async ({ id, ...updatedData }, context) => {

  if (!context.user) {
    throw new HttpError(401, 'Not authorized');
  }

  const updated = await context.entities.Foo.update({
    where: { 
      id,
    },
    data: {
      updatedData,
    }
  });

export const updateFoo: UpdateFoo<{
  id: string;
  bar?: string;
}, Foo> = async ({ id, ...updatedData }, context) => {

  if (!context.user) {
    throw new HttpError(401, 'Not authorized');
  }

  const updated = await context.entities.Foo.update({
    where: { 
      id,
    },
    data: {
      updatedData,
    }
  });

I have a Zod schema in the front-end code

formSchema = z
  .object({
    title: z.string().optional().nullable()
})

formSchema = z
  .object({
    title: z.string().optional().nullable()
})

In my form if I clear the value of

bar

bar

it generates the following for

updatedData

updatedData

{
  bar: undefined
}

{
  bar: undefined
}

As a result

bar

bar

will be ignored in the Prisma update and so it doesn't clear to null.

What's best practise here?:
1. Do I need to find a way to get Zod to generate null for empty fields (I've tried)
2. Or do I need to convert fields that are undefined to null in the

updatedData

updatedData

object before using Prisma to update the object.

I've read this https://www.prisma.io/docs/orm/prisma-client/special-fields-and-types/null-and-undefined which indicates that undefined should be avoided in Primsa.

Null and undefined in Prisma Client (Reference) | Prisma Documentation

How Prisma Client handles null and undefined

Best way to generate null form values for a Prisma update

Not sure best place to ask this question, but I figure developers building CRUD forms in wasp might have the same question.

I have an entity like this:

model Foo {
  id String @id @default(uuid(7))
  bar String? 
}

model Foo {
  id String @id @default(uuid(7))
  bar String? 
}

I'm updating the entity like this in the back-end:

export const updateFoo: UpdateFoo<{
  id: string;
  bar?: string;
}, Foo> = async ({ id, ...updatedData }, context) => {

  if (!context.user) {
    throw new HttpError(401, 'Not authorized');
  }

  const updated = await context.entities.Foo.update({
    where: { 
      id,
    },
    data: {
      updatedData,
    }
  });

export const updateFoo: UpdateFoo<{
  id: string;
  bar?: string;
}, Foo> = async ({ id, ...updatedData }, context) => {

  if (!context.user) {
    throw new HttpError(401, 'Not authorized');
  }

  const updated = await context.entities.Foo.update({
    where: { 
      id,
    },
    data: {
      updatedData,
    }
  });

I have a Zod schema in the front-end code

formSchema = z
  .object({
    title: z.string().optional().nullable()
})

formSchema = z
  .object({
    title: z.string().optional().nullable()
})

In my form if I clear the value of

bar

bar

it generates the following for

updatedData

updatedData

{
  bar: undefined
}

{
  bar: undefined
}

As a result

bar

bar

updatedData

updatedData

Null and undefined in Prisma Client (Reference) | Prisma Documentation

How Prisma Client handles null and undefined

Best way to generate null form values for a Prisma update

Similar Threads

Best way to generate null form values for a Prisma update

Similar Threads

Similar Threads

Similar Threads