-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Updated keystone-next dev so that it interactively prompts for creating and applying a migration #5135
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/keystonejs/keystone-next-docs/CkX7KCHmUCD7Lp9Lhk7nabF2hsLT |
🦋 Changeset detectedLatest commit: 27d41e4 The changes in this PR will be included in the next version bump. This PR includes changesets to release 24 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 27d41e4:
|
Co-authored-by: Tim Leslie <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few final nits, but other than that I think we can 🚢 this 👍
Co-authored-by: Tim Leslie <[email protected]>
This is mostly based on the implementation of the actual
prisma migrate dev
command but not doing things that prisma does(e.g. reading the schema from the file system)keystone.next.dev.with.prisma.migrate.mp4