Prisma generated code fails @typescript-eslint/no-unsafe-call and @typescript-eslint/no-unsafe-assignment eslint rules

[magnusottosson]

Question

I have the eslint rules @typescript-eslint/no-unsafe-assignment and @typescript-eslint/no-unsafe-call turned on and when I query the prisma interface these rules fails.

I dont really see why the generated prisma models fails on these eslint rules?

How to reproduce (optional)

No response

Expected behavior (optional)

No response

Information about Prisma Schema, Client Queries and Environment (optional)

generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider                       = "postgresql"
  url                                 = env("DATABASE_URL")
  shadowDatabaseUrl   = env("SHADOW_DATABASE_URL")
}

model Foo {
  bar String @id
}

const prisma = new PrismaClient();

const data: Prisma.FooUncheckedCreateInput = {
    bar: 'hello',
 };

// Unsafe assignment of an `any` value.eslint[@typescript-eslint/no-unsafe-assignment](https://typescript-eslint.io/rules/no-unsafe-assignment)
const args: Prisma.FooCreateArgs = {
  data,
 };

// Unsafe call of an `any` typed value.eslint[@typescript-eslint/no-unsafe-call](https://typescript-eslint.io/rules/no-unsafe-call)
prisma.foo.create(args);

• OS: macOS
• Database: PostgreSQL
• Node.js version: 18

prisma                  : 5.4.2
@prisma/client          : 5.4.2
Current platform        : darwin-arm64
Query Engine (Node-API) : libquery-engine ac9d7041ed77bcc8a8dbd2ab6616b39013829574 (at node_modules/@prisma/engines/libquery_engine-darwin-arm64.dylib.node)
Schema Engine           : schema-engine-cli ac9d7041ed77bcc8a8dbd2ab6616b39013829574 (at node_modules/@prisma/engines/schema-engine-darwin-arm64)
Schema Wasm             : @prisma/prisma-schema-wasm 5.4.1-2.ac9d7041ed77bcc8a8dbd2ab6616b39013829574
Default Engines Hash    : ac9d7041ed77bcc8a8dbd2ab6616b39013829574
Studio                  : 0.494.0

[magnusottosson]

NVM, seems like it was a hickup in vs code. After a restart the error is gone..

[charlescrain]

Same thing, try restarting VS code. Just doing the TS server did not fix it.