Prisma VSCode extension combines multiple copies of the same schema and throws errors

[Arlen22]

The Prisma VS Code extension treats multiple copies of the same schema as though they are supposed to be separate files in a multi-file schema, and then complains that everything has duplicate names. This is especially annoying when I use a custom output directory that is within the detected source code of my project as it will often automatically detect the schema without me even opening it, and then I have red folders which I open to check the problem, only to realize it's just the schema being detected.

[igalklebanov]

Hey 👋

Could you provide a minimal repository that reproduces what you're experiencing?

[Arlen22]

put the following schema in a parent and child folder (so the second schema's folder is sibling to the first folder)

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

enum BranchUserLevel {
  user
  admin
}

If that doesn't cause it to happen, try adding the generator block to one of them so they aren't byte identical.

[fornaeffe]

I don't know if it is exactly the same issue @Arlen22 encountered, but I can reproduce a very similar issue with this repo:
https://github.com/fornaeffe/minrepex_prisma_vscode_ext

To reproduce:

npm install
npx prisma generate

Open prisma/schema.prisma in VSCode with Prisma extension

When in the root of the repo there is another .prisma file (not used in client generation), and prisma-client-js is used as generator, it will flag errors in prisma/schema.prisma file because it finds them duplicated in the generated/client/schema.prisma file. It was quite hard to figure out that the problem was not in prisma/schema.prisma nor in generated files, but in the unused .prisma file.

[Arlen22]

Now it's just straight up throwing the error when I literally can't find a second copy. Can you give me some debug instructions for this?

[Arlen22]

@igalklebanov Is there a way for me to turn on debugging to determine where the second file is coming from?

[fornaeffe]

Now it's just straight up throwing the error when I literally can't find a second copy. Can you give me some debug instructions for this?

For me, the solution was to remove another .prisma file that I previously put in the project root directory, not involved in prisma client generation. Note that errors were not marked in that file, but in my main schema.prisma, and the two files didn't have any conflicting models. Perhaps you have some .prisma files other that the schema used for client generation?

[Arlen22]

I really think there needs to be some VSCode settings that can restrict the Prisma plugin to only look in certain folders and ignore all others. If it's a setting it can be set per workspace or folder. If it's not going to respect the prisma.config.ts file it should at least do that.

[Arlen22]

This was a really big deal with the prisma-client-js provider, which ended up having two or three copies scattered around the repo, so it was always detecting the other files. I've switched to prisma-client now, which doesn't include a schema file in the build output, thankfully. But I don't think that's the right approach because there could be other reasons people copy that file.

[Arlen22]

Never mind, I thought for a second that removing all other prisma files would fix it, but it still hasn't. There's no way to figure out where the other prisma files supposedly are because it doesn't link to them.

@igalklebanov How can I debug this in my install or repo? I can give you a GitHub repo but I can't reproduce it in codespaces. Hopefully you can reproduce it in VSCode.

https://github.com/TiddlyWiki/MultiWikiServer/tree/d9b15f3939c3f70c4f6ba6d4c40b64bbe2b97865

It really feels like it's recursively finding the same file. Like a variable isn't being cleared before a run or something.

[Arlen22]

Still experiencing this on the latest version of the prisma plugin, despite now having a prisma.config.ts file in the root folder. Commands using the prisma.config.ts file do not throw this error, only the language server. It's in the language server, based on "Restart language server" clearing the error for a few seconds.

How has this not been reproduced? I've had this same problem in every single repo for months.

[Arlen22]

Hey 👋

Could you provide a minimal repository that reproduces what you're experiencing?

@igalklebanov I've never NOT had this problem. How is this not reproduced by default?