Chip Clark
10/20/2021, 2:47 PMUnknown arg `id` in data.id for type MainSidebarUpdateInput. Available args:
type MainSidebarUpdateInput {
Main_Sidebar?: String | NullableStringFieldUpdateOperationsInput | Null
}
+34621ms
Error:
Invalid `prisma.mainSidebar.update()` invocation:
{
where: { ID: 1 }
service:
async updateMainSidebar(params: {
where: Prisma.MainSidebarWhereUniqueInput;
data: Prisma.MainSidebarUpdateInput;
}) {
const { where, data } = params;
return this.prisma.mainSidebar.update({
where,
data
});
}
controller:
@Put(`${Route}/:id`)
async update(
@Param('id', ParseIntPipe) ID: number,
@Body() data: Prisma.MainSidebarUpdateInput
) {
return this.mainSidebarService.updateMainSidebar({
where: { ID },
data,
});
}
schema
model MainSidebar {
ID Int @id @default(autoincrement())
Main_Sidebar String? @db.VarChar(Max)
}
Application side error:
HttpErrorResponse: {"headers":{"normalizedNames":{},"lazyUpdate":null},"status":500,"statusText":"Internal Server Error","url":"<http://am-web11:3060/api/sidebar/1>","ok":false,"name":"HttpErrorResponse","message":"Http failure response for <http://am-web11:3060/api/sidebar/1>: 500 Internal Server Error","error":{"statusCode":500,"message":"Internal server error"}}
Austin
10/20/2021, 8:29 PM@id
field (primary key) like ID
in your case. If you look at MainSidebarUpdateInput
, you will see that ID
is not present on that type for this reason.Chip Clark
10/20/2021, 9:59 PM