Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
janpio opened this issue May 28, 2020 · 2 comments
Open

Comments

@janpio
Copy link
Member

janpio commented May 28, 2020

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 indicator in VSCode to do this would be nice.

Random idea: Have a traffic light like indicator that goes from green to red when you modified your schema and did not regenerate your Client yet.

@janpio janpio added kind/feature A request for a new feature. topic: ui labels May 28, 2020
@janpio janpio changed the title Indicator that you change the schema but did not regenerate the Client Indicator that you changed the schema but did not regenerate the Client May 28, 2020
@janpio
Copy link
Member Author

janpio commented May 28, 2020

(Same idea could be applied to Migrate when it exists)

@Jolg42 Jolg42 added the team/schema Issue for team Schema. label Nov 16, 2021
@janpio janpio moved this from DX to Prisma Client related in 🌐 Language Tools Issue Categorization Nov 24, 2021
@Jolg42 Jolg42 added the process/candidate Candidate for next Milestone. label Dec 22, 2021
@jpaas
Copy link

jpaas commented Dec 23, 2021

Or even better, the extension could watch the schema and regenerate automatically

@janpio janpio removed the process/candidate Candidate for next Milestone. label Jan 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature A request for a new feature. team/schema Issue for team Schema. topic: prisma client topic: ui
Projects
Development

No branches or pull requests

3 participants