-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VSCode extension panics when opening an empty prisma schema #1760
Labels
bug/2-confirmed
Bug has been reproduced and confirmed.
domain/schema
Issue in the "Schema" domain: Prisma Schema, Introspection, Migrations etc.
kind/regression
A reported bug in functionality that used to work before.
topic: linting
topic: wasm
Milestone
Comments
Druue
added
bug/2-confirmed
Bug has been reproduced and confirmed.
kind/regression
A reported bug in functionality that used to work before.
topic: linting
domain/schema
Issue in the "Schema" domain: Prisma Schema, Introspection, Migrations etc.
topic: wasm
labels
Jun 12, 2024
This was referenced Aug 21, 2024
This was referenced Aug 24, 2024
This was referenced Sep 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug/2-confirmed
Bug has been reproduced and confirmed.
domain/schema
Issue in the "Schema" domain: Prisma Schema, Introspection, Migrations etc.
kind/regression
A reported bug in functionality that used to work before.
topic: linting
topic: wasm
Bug description
Highlighted here
Opening an empty prisma schema file i.e.
Yields the following error pop-up
With the following details in
output
How to reproduce
5.15.0
of the vscode extensionExpected behavior
It shouldn't panic
Environment & setup
v1.88.1
v5.15.0
The text was updated successfully, but these errors were encountered: