Prisma types are not regeneraetd until Visual Studio Code restarts

Bug description

When adding a new model to my schema, Visual Studio Code fails to realize that I can use this as a property on the prisma object until I restart the program. Perhaps this is a Visual Studio Code bug instead? Sorry if so and feel free to close.

How to reproduce

1. Open schema and a .ts file in Visual Studio Code
2. Add a model to your schema, or change the name of your schema
3. Try to find the new or renamed schema in your .ts file
4. It cannot

Expected behavior

I would expect the new schema values to be available in my .ts files.

Prisma information

No special schema in place. You can reproduce this with this simple code in your .ts file:

const test = await prisma.schemaName.findMany();

Environment & setup

• OS: Mac OS
• Database: SQLite
• Node.js version: v14.4.0
• Prisma version

2.21.2

[theowiersema]

Hmm. Well if I ever come across another reproducible case I’ll attempt to document it. In the meantime, when in doubt I can just npx prisma generate excessively 😉

[janpio]

VSCode and Typescript are not super big friends when it comes to reload type definitions. We actually do some fancy stuff in our VSCode extension to try to work around that, but it does not work all the time (and unfortunately there is no way for us to recognize). Maybe you hit one of these cases.