You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This bug is particularly related with the VSCode extension for Prisma. When trying to autocomplete relations across different files, we need to trigger it once from both sides of the relation.
When its a single file, it works as expected, autocompleting both.
Severity
🔹 Minor: Unexpected behavior, but does not block development
Reproduction
prisma.autocomplete.mp4
Expected vs. Actual Behavior
Should autocomplete both sides directly.
Only completes the current file's relation.
Frequency
Consistently reproducible
Does this occur in development or production?
Only in development (e.g., CLI tools, migrations, Prisma Studio)
Is this a regression?
I'm not sure. But probably not as far as I know.
Workaround
Just trigger autocomplete in both files sequentially.
Bug description
This bug is particularly related with the VSCode extension for Prisma. When trying to autocomplete relations across different files, we need to trigger it once from both sides of the relation.
When its a single file, it works as expected, autocompleting both.
Severity
🔹 Minor: Unexpected behavior, but does not block development
Reproduction
prisma.autocomplete.mp4
Expected vs. Actual Behavior
Should autocomplete both sides directly.
Only completes the current file's relation.
Frequency
Consistently reproducible
Does this occur in development or production?
Only in development (e.g., CLI tools, migrations, Prisma Studio)
Is this a regression?
I'm not sure. But probably not as far as I know.
Workaround
Just trigger autocomplete in both files sequentially.
Prisma Schema & Queries
schema.prismaother.prismaPrisma Config
Logs & Debug Info
Environment & Setup
Not needed, can be reproduced without any setup.
Prisma Version