-
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
Restore resolvedData types #7833
Conversation
🦋 Changeset detectedLatest commit: 153698d The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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 153698d:
|
f0b488e
to
926bc79
Compare
926bc79
to
19cd173
Compare
19cd173
to
e24c535
Compare
4865517
to
a57d96d
Compare
7b49a2f
to
153698d
Compare
Co-authored-by: Daniel Cousens <dcousens@users.noreply.github.com>
Co-authored-by: Daniel Cousens <dcousens@users.noreply.github.com>
Co-authored-by: Daniel Cousens <dcousens@users.noreply.github.com>
The
resolvedData
types were identified as being actively misleading in #7801.This pull request restores the types, and now matches what Keystone actually expects and provides to end developers.
The new types approximately mirror the prisma types, but are slightly different for database fields with
kind: 'multi'
(multi-column fields) that Keystone and different field types often use.resolvedData
in hooks should use Prisma create/update types #7691