Remove id from resolvedData types

[emmatown]

This pull request removes id from the new (fixed) resolvedData types (see #7833).

id is not something you can safely change through these interim types, a by product of autoIncrement fields in Prisma not containing an id in the resultant Prisma types.

The types previously were wrong enough that we are not considering this a breaking change, as it only refines our types to be representative of the constraints in effect, and is not a change in behaviour. If you relied on this unsafe behaviour, you can cast away the types at your own peril.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
keystone-next-docs	✅ Ready (Inspect)	Visit Preview	Sep 15, 2022 at 6:02AM (UTC)

[changeset-bot]

⚠️ No Changeset found

Latest commit: e928280

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codesandbox-ci]

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 e928280:

Sandbox	Source
@keystone-6/sandbox	Configuration