-
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
Replace keystone-next prototype with keystone-next dev and a config option to determine if migrations should be used or not #5163
Replace keystone-next prototype with keystone-next dev and a config option to determine if migrations should be used or not #5163
Conversation
…ption to determine if migrations should be used or not
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/keystonejs/keystone-next-docs/GepS4s4icPr4AyFDLFJ52mEuSmKr |
🦋 Changeset detectedLatest commit: 2726276 The changes in this PR will be included in the next version bump. This PR includes changesets to release 18 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 2726276:
|
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.
Looks good 👍
Currently, it's not very clear what people should use and what
keystone-next prototype
is and isn't compatible with, this PR makes it clear what command you should run and what commands you can't use if you're not using migrations. For example, we had an example that haddev
andprototype
scripts which doesn't make sense since they're mutually exclusive workflows. This replaceskeystone-next prototype
with adb.useMigrations
option to determine if Keystone should use migrations or push the schema with the potential for data loss.