Skip to content

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

@Arlen22

Description

@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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bug/0-unknownBug is new, does not have information for reproduction or reproduction could not be confirmed.domain/schemaIssue in the "Schema" domain: Prisma Schema, Introspection, Migrations etc.priority/unknownWe've seen this issue but we're not about the prioritysize/unknownWe've seen this issue but we're not sure how long it will take

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions