enum fields are missing in select's type when clientExtensions preview feature is used

[gtolarc]

Bug description

An error that did not exist in 4.6.1 occurs after upgrading to 4.7, and it seems that enum type fields are missing in select.

How to reproduce

v4.6.1

v4.7

"kind" field (enum) is missing

Expected behavior

No response

Prisma information

enum GameKind {
  KIND1
  KIND2
}

model Game {
  id   Int      @id @default(autoincrement())
  name String
  kind GameKind @default(KIND1)

  status Json @default("{}")

  grade   GameGrade? @relation(fields: [gradeId], references: [id])
  gradeId Int?

  tournament  Tournament?
  userProfits UserProfits[]

  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt

  @@unique([name, kind])
  @@map(name: "game")
}

Environment & setup

• OS: macOS
• Database: PostgreSQL
• Node.js version: v19.1.0

Prisma Version

prisma                  : 4.7.0
@prisma/client          : 4.7.0
Current platform        : darwin-arm64
Query Engine (Node-API) : libquery-engine 39190b250ebc338586e25e6da45e5e783bc8a635 (at node_modules/prisma/node_modules/@prisma/engines/libquery_engine-darwin-arm64.dylib.node)
Migration Engine        : migration-engine-cli 39190b250ebc338586e25e6da45e5e783bc8a635 (at node_modules/prisma/node_modules/@prisma/engines/migration-engine-darwin-arm64)
Introspection Engine    : introspection-core 39190b250ebc338586e25e6da45e5e783bc8a635 (at node_modules/prisma/node_modules/@prisma/engines/introspection-engine-darwin-arm64)
Format Binary           : prisma-fmt 39190b250ebc338586e25e6da45e5e783bc8a635 (at node_modules/prisma/node_modules/@prisma/engines/prisma-fmt-darwin-arm64)
Format Wasm             : @prisma/prisma-fmt-wasm 4.7.0-74.39190b250ebc338586e25e6da45e5e783bc8a635
Default Engines Hash    : 39190b250ebc338586e25e6da45e5e783bc8a635
Studio                  : 0.477.0

[SevInf]

Hey @gtolarc and everybody else affected.
Thank you for the report!. We identified and fixed the issue. It will come out in 4.8.1 release later todaytomorrow.
Unitl that happens, you could disable clientExtensions preview feature - bug occurs only when it is used.

[SevInf]

4.7.1 is released, now it should work correctly even if clientExtensions preview feature is used.