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

Updates to schema.prisma in dev mode require for the studio to work #1006

Closed
2color opened this issue Nov 27, 2019 · 3 comments
Closed

Updates to schema.prisma in dev mode require for the studio to work #1006

2color opened this issue Nov 27, 2019 · 3 comments
Assignees
Labels
bug/2-confirmed Bug has been reproduced and confirmed. kind/bug A reported bug.
Milestone

Comments

@2color
Copy link
Contributor

2color commented Nov 27, 2019

Problem

While initialising a new project with the JavaScript GraphQL starter script I encountered a problem with migrations.
When a new field is added, the CLI automatically runs the migration and re-generates the client library, however, the studio throws an error when the browser is reloaded.

In the following example, I added a facebook field and reloaded the browser.

Screen Shot 2019-11-27 at 12 45 57 pm

Suggested Solution

The problem is solved by stoping prisma dev and running it again. Perhaps it makes sense to automatically reload the studio?

@timsuchanek
Copy link
Contributor

Thanks for reporting @2color and you report this in the perfect timing. We'll release a patch for this within the next 30 min :)
I'll notify you here in the issue and close it once we've released it.

@pantharshit00 pantharshit00 added bug/2-confirmed Bug has been reproduced and confirmed. kind/bug A reported bug. labels Nov 27, 2019
@timsuchanek timsuchanek added this to the Preview 18 milestone Nov 27, 2019
@timsuchanek timsuchanek self-assigned this Nov 27, 2019
@timsuchanek
Copy link
Contributor

The patch is out! https://github.com/prisma/prisma2/releases/tag/2.0.0-preview017.1

@2color
Copy link
Contributor Author

2color commented Nov 27, 2019

@timsuchanek Can you link to the commit with the fix? I'm curious to see how it was resolved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug/2-confirmed Bug has been reproduced and confirmed. kind/bug A reported bug.
Projects
None yet
Development

No branches or pull requests

3 participants