-
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
feat(LS): references #1775
feat(LS): references #1775
Conversation
🤖 Pull request artifactsempty string
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing console.log
, otherwise looks good!
I've tested that a bit in a GitPod and i thing references for the fields works a little bit backwards from how I am expecting them to: I have 3 files: // config.prisma
generator client {
provider = "prisma-client-js"
previewFeatures = ["prismaSchemaFolder"]
}
datasource db {
provider = "sqlite"
url = "file:dev.db"
}
// User.prisma
model User {
id String @id
name String
posts Post[]
}
// Post.prisma
model Post {
id String @id
title String
authorId String
author User @relation(fields: [authorId], references: [id])
} When I look for references of |
Co-authored-by: Serhii Tatarintsev <[email protected]>
To test this locally:
npm i && npm run bootstrap
in the root of language-tools2../prisma-schema-wasm/scripts/update-schema-wasm.sh
in the root of enginesnpm run compile
in the root of language-toolsLaunch VS Code extension
3.5 if you see the the following error message:
cd packages/language-server
tsc -p ./
and re-try launching the extensioncompanion pr to prisma/prisma-engines#4934