I used to be able to drop a column / table in a Prisma migration and running a npx prisma generate would properly update the kysely.ts by removing the fields that aren't in my table anymore (like a full alignment between my schema.prisma file and the kysely.ts.
Since a couple of weeks, the Kysely generated fields stay after I drop a column and generate the Kysely types anew with the above command.
No changes seem to have taken place on the prisma-kysely package since it's been inactive for 8 months.
Could it be coming from a Prisma upgrade?
Having a 1-to-1 sync between schema and Kysely types really is a must.
I have a Prisma schema with a Kysely generator as follows:
I used to be able to drop a column / table in a Prisma migration and running a
npx prisma generate
would properly update thekysely.ts
by removing the fields that aren't in my table anymore (like a full alignment between myschema.prisma
file and thekysely.ts
.Since a couple of weeks, the Kysely generated fields stay after I drop a column and generate the Kysely types anew with the above command.
No changes seem to have taken place on the
prisma-kysely
package since it's been inactive for 8 months. Could it be coming from a Prisma upgrade?Having a 1-to-1 sync between schema and Kysely types really is a must.