Jan Piotrowski

 Observed in preview `21.0.15` (which corresponds to our CLI 2.21.0-dev.21).

Auto completion suggests `@map` although already present

1

For reproduction: ```prisma generator client { provider = "prisma-client-js" previewFeatures = "mongoDb" } datasource pg { provider = "mongodb" url = env("TEST_DB_URL") } model with_id_and_compound_unique { id Int @id @map("_id")...

Syntax Highlighting fails after `@default("\"")`

4

This is the schema: ``` generator client { provider = "prisma-client-js" previewFeatures = ["extendedIndexes", "fullTextIndex"] } datasource db { provider = "mysql" url = "..." } model index_5e404df0a4aa1 { id...

MongoDB: Quick fix for missing `@map("_id")` annotation

3


Currently creating a relation from just the relation scalar (foreign key) field is pretty meh. Could be: Click + Type (for target model) + optional references + then cursor on...

https://code.visualstudio.com/docs/getstarted/userinterface#_outline-view  Could list the top level blocks like `generator`, `datasource`, `model` and so on with their names. Possibly implementable via this: https://stackoverflow.com/a/59132169

 The missing bits in the schema could (partially) shown in a similar way to this.

Indicator that you changed the schema but did not regenerate the Client

2

When you modify your schema, you also need to `prisma generate` so that your Prisma Client still works with your database. This tends to be forgotten quite often, so an...

Improve local development workflow and update documentation

2

- How to use local Language Tools build in local VSCode extension? - How to use a local `prisma-fmt` Wasm module? - ...