-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Add map support to lists and fields #6907
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
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/keystonejs/keystone-next-docs/DnGcUJ4CjZvVJYQ8huS3tb9JERek |
🦋 Changeset detectedLatest commit: 1b74e5f The changes in this PR will be included in the next version bump. This PR includes changesets to release 15 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. |
Co-authored-by: Daniel Cousens <413395+dcousens@users.noreply.github.com>
Adds
config.db.map
to lists and mode fields types, which adds@map
and@@map
annotations to the Prisma schema, and lets you use different table and column names to those automatically chosen by Keystone based on your list and field keys.