Bug description

Around 6.6 the linter is starting to complain about schema files in the migrations folder that are being picked up by the linter. I'm using a data-migrations package https://github.com/Softjey/prisma-dm that packs up the schema and bundles it in the migration folder to use as migration specific prisma clients.

The errors are about duplicate generators, tables, and such.

i've tried specifying a schema in package.json (which I didn't have before and worked without)

I'm not sure how to get the functionality that I had before which was this:

/migrations
  /923989123_1
        /migration.sql
        /schema.prisma
/schema
  /schema.prisma
  /account.prisma
  /user.prisma

and not have the linter explode that schemas in the migrations folder are interfering and viceversa. I would have thought migrations would have been ignored.

Severity

⚠️ Major: Breaks core functionality (e.g., migrations fail)

Reproduction

having a schema file in the migrations folder causes this issue.

Expected vs. Actual Behavior

linting should not be complaining.

Frequency

Consistently reproducible

Does this occur in development or production?

Both development and production

Is this a regression?

this worked on 5.18.0 with previewFeatures = ["prismaSchemaFolder"] specified and now with it removed and on 6.7.0 does not work

Workaround

downgrading to 5.18.0

Prisma Schema & Queries

not needed

Prisma Config

i don't have one.

Logs & Debug Info

none

Environment & Setup

doesn't matter

Prisma Version

not applicable