Prisma extension lagging after changing to a multi-file schema

ORM

Hello, I followed the documentation to create a multi-file schema using the following structure:

prisma/
├── migrations
├── models
│   ├── user.prisma
│   ├── announcement.prisma
│   ├── event.prisma
│   └── post.prisma
└── schema.prisma

prisma/
├── migrations
├── models
│   ├── user.prisma
│   ├── announcement.prisma
│   ├── event.prisma
│   └── post.prisma
└── schema.prisma

I updated the prisma config file as per the documentation:

import "dotenv/config"
import { defineConfig, env } from "prisma/config"

export default defineConfig({
  schema: "prisma/",
  migrations: {
    path: "prisma/migrations",
  },
  datasource: {
    url: env("DATABASE_URL"),
  },
})

import "dotenv/config"
import { defineConfig, env } from "prisma/config"

export default defineConfig({
  schema: "prisma/",
  migrations: {
    path: "prisma/migrations",
  },
  datasource: {
    url: env("DATABASE_URL"),
  },
})

However after these changes, I've noticed that editing any of the schema files is near to impossible as the Prisma extension repeatedly runs

lint()

lint()

multiple times per single save and continues to hang.

Then I reverted back to using a single schema file and this still cause issues with the extension, where it would take a few seconds to suggest autocompletions for types and provide linting errors; these were resolved after I recently remembered to change back the config file to

schema: "prisma/schema.prisma"

schema: "prisma/schema.prisma"

.

Prior to changing the config file after I had reverted to using a single file, it seemed as if linting was happening with every keystroke as the error message slowly updated with each character of a variable I had typed.

The extension works fine with a single schema file, with the config set to

schema: "prisma/schema.prisma

schema: "prisma/schema.prisma

, however I would really like to split my schema up into multiple files if possible. I wasn't too sure if this was a known issue or not as I've seen similar issues on Github, thought it would be better to ask on Discord shrug

Prisma•2mo ago•

10 replies

TiltedMinds

Prisma extension lagging after changing to a multi-file schema

ORM

Hello, I followed the documentation to create a multi-file schema using the following structure:

prisma/
├── migrations
├── models
│   ├── user.prisma
│   ├── announcement.prisma
│   ├── event.prisma
│   └── post.prisma
└── schema.prisma

prisma/
├── migrations
├── models
│   ├── user.prisma
│   ├── announcement.prisma
│   ├── event.prisma
│   └── post.prisma
└── schema.prisma

I updated the prisma config file as per the documentation:

import "dotenv/config"
import { defineConfig, env } from "prisma/config"

export default defineConfig({
  schema: "prisma/",
  migrations: {
    path: "prisma/migrations",
  },
  datasource: {
    url: env("DATABASE_URL"),
  },
})

import "dotenv/config"
import { defineConfig, env } from "prisma/config"

export default defineConfig({
  schema: "prisma/",
  migrations: {
    path: "prisma/migrations",
  },
  datasource: {
    url: env("DATABASE_URL"),
  },
})

However after these changes, I've noticed that editing any of the schema files is near to impossible as the Prisma extension repeatedly runs

lint()

lint()

schema: "prisma/schema.prisma"

schema: "prisma/schema.prisma"

schema: "prisma/schema.prisma

schema: "prisma/schema.prisma

Prisma extension lagging after changing to a multi-file schema

Similar Threads

Prisma extension lagging after changing to a multi-file schema

Similar Threads

Similar Threads

Similar Threads