prisma / language-tools

🌐 Prisma Language Tools = Language Server and Prisma's VS Code extension.

Home Page:https://marketplace.visualstudio.com/items?itemName=Prisma.prisma

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

The preview feature "relationJoins" is not known.

SC0d3r opened this issue · comments

Bug description

After updating to version 5.7.0, whenever I add relationJoins to the previewFeatures, a red line appears, indicating the following:

"The preview feature "relationJoins" is not known. Expected one of: deno, driverAdapters, fullTextIndex, fullTextSearch, metrics, multiSchema, postgresqlExtensions, tracing, views"

It does not interfere with npx prisma generate, as it is merely a visual bug. Is this issue specific to me? I have not come across any related problems during my search.

Sun 10 Dec 2023 12_19_24 PM +0330

How to reproduce

  1. Go to vscode and schema.prisma file
  2. Add "relationJoins" in previewFeatures

Expected behavior

"relationJoins" is considered a known preview feature.

Prisma information

<! -- >

Environment & setup

  • OS: Debian
  • Database: PostgreSQL
  • Node.js version: 18.16.0

Prisma Version

Environment variables loaded from .env
prisma                  : 5.7.0
@prisma/client          : 5.7.0
Computed binaryTarget   : debian-openssl-1.1.x
Operating System        : linux
Architecture            : x64
Node.js                 : v18.16.0
Query Engine (Node-API) : libquery-engine 79fb5193cf0a8fdbef536e4b4a159cad677ab1b9 (at node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node)
Schema Engine           : schema-engine-cli 79fb5193cf0a8fdbef536e4b4a159cad677ab1b9 (at node_modules/@prisma/engines/schema-engine-debian-openssl-1.1.x)
Schema Wasm             : @prisma/prisma-schema-wasm 5.7.0-41.79fb5193cf0a8fdbef536e4b4a159cad677ab1b9
Default Engines Hash    : 79fb5193cf0a8fdbef536e4b4a159cad677ab1b9
Studio                  : 0.495.0
Preview Features        : fullTextSearch, relationJoins

The line comes from the VS Code extension. Did you (or actually VS Code itself, it usually manages version updates automatically) also upgrade that one to the most recent version?

Should be a way to set what version of Prisma the extension actually uses

@janpio, I am pleased to inform you that the mentioned issue has been satisfactorily resolved. Consequently, I request that we proceed with its closure. Thank you for your attention to this matter.

@Allakazan You just install the equivalent Prisma extension version - they use the same version numbers for that reason.

@SC0d3r Thanks for letting us know <3