New core

.changeset/bright-eels-wash.md

@@ -0,0 +1,5 @@
+---
+'@keystone-next/keystone': major
+---
+
+The ordering of types in the generated `schema.graphql` has changed due to the re-implementation of the core of Keystone, you will need to run `keystone-next dev`/`keystone-next postinstall --fix` to update it.

.changeset/few-hounds-doubt.md

@@ -0,0 +1,5 @@
+---
+'@keystone-next/keystone': major
+---
+
+`createSystem` no longer accepts a Prisma client directly and it returns `getKeystone` which accepts the generated Prisma client and returns `connect`, `disconnect` and `createContext` instead of returning a `keystone` instance object.

.changeset/little-chicken-beg.md

@@ -0,0 +1,5 @@
+---
+'@keystone-next/fields': major
+---
+
+The relationship field now returns a `[Item!]` instead of a `[Item!]!`, this is so that if an error occurs when resolving the related items, only the relationship field will be returned as null rather than the whole item being returned as null.

.changeset/mean-chairs-destroy.md

@@ -0,0 +1,5 @@
+---
+'@keystone-next/fields': major
+---
+
+The API to configure `virtual` fields has changed to accept a `field` using the `schema` API exported from `@keystone-next/types` rather than GraphQL SDL. 

.changeset/plenty-flies-think.md

@@ -0,0 +1,10 @@
+---
+'@keystone-next/auth': major
+'@keystone-next/cloudinary': major
+'@keystone-next/fields': major
+'@keystone-next/fields-document': major
+'@keystone-next/keystone': major
+'@keystone-next/types': major
+---
+
+The core of Keystone has been re-implemented to make implementing fields and new features in Keystone easier. While the observable changes for most users should be minimal, there could be breakage. If you implemented a custom field type, you will need to change it to the new API, see fields in the `@keystone-next/fields` package for inspiration on how to do this.

.changeset/rare-coats-learn.md

@@ -0,0 +1,5 @@
+---
+'@keystone-next/keystone': major
+---
+
+The ordering of relationships fields in the generated Prisma schema has changed so that it aligns with the order specified in the list config with the opposites to one-sided relationships added at the end. The name of one-to-one and one-to-many relationships has also changed to include `_` between the list key and field key to align with many-to-many relationships. Note that these changes do **not require a migration**, only your `schema.prisma` file will need to be updated with `keystone-next dev`/`keystone-next postinstall --fix`.

.changeset/rich-worms-accept.md

@@ -0,0 +1,5 @@
+---
+'@keystone-next/keystone': major
+---
+
+The `id` field on the item returned from `context.db.lists` functions/passed to hooks/field type resolvers is now whatever the actual id field returned from Prisma is rather than a stringified version of it.

.changeset/six-colts-give.md

@@ -0,0 +1,6 @@
+---
+'@keystone-next/keystone': major
+'@keystone-next/types': major
+---
+
+Replaced `graphql.itemQueryName` with always using the list key as the singular name in GraphQL and renamed `graphql.listQueryName` to `graphql.plural`

.changeset/slow-camels-fold.md

@@ -0,0 +1,6 @@
+---
+'@keystone-next/keystone': major
+'@keystone-next/types': major
+---
+
+The `KeystoneContext` type no longer has the `keystone` object or functions to run access control.

.changeset/small-guests-relate.md

@@ -0,0 +1,6 @@
+---
+'@keystone-next/keystone': major
+'@keystone-next/types': major
+---
+
+List level create, update and delete access control is now called for each operation in a many operation rather than on all of the operations as a whole. This means that rather than recieving originalInput as an array with itemIds, your access control functions will always be called with just an itemId and/or originalInput(depending on which access control function it is). If your access control functions already worked with creating/updating/deleting one item, they will continue working (though you may get TypeScript errors if you were previously handling itemIds and originalInput as an array, to fix that, you should stop handling that case).

.changeset/smooth-pears-float.md

@@ -0,0 +1,15 @@
+---
+'@keystone-next/fields': major
+---
+
+The `password` field type now adds a GraphQL type `PasswordState` to the GraphQL output type instead of adding `${fieldKey}_is_set`.
+
+```graphql
+type User {
+  password: PasswordState
+}
+
+type PasswordState {
+  isSet: Boolean!
+}
+```

.changeset/thin-humans-cheat.md

@@ -0,0 +1,6 @@
+---
+'@keystone-next/auth': major
+'@keystone-next/fields': major
+---
+
+The way that the implementations of `generateHash` and `compare` are passed from the password field to auth has changed to be in the extensions object of the GraphQL output field. Unless you've written your own password field implementation or you're using mismatching versions of @keystone-next/auth and @keystone-next/fields, this won't affect you.

.changeset/wicked-moles-cough.md

@@ -0,0 +1,5 @@
+---
+'@keystone-next/keystone': major
+---
+
+Filters returned from access control now go through GraphQL validation and coercion like filters that you pass in through the GraphQL API, this will produce better errors when you return invalid values.

docs/pages/apis/access-control.mdx

@@ -147,20 +147,14 @@ export default config({
 
 Imperative access control functions are passed a collection of arguments which can be used to determine whether the operation is allowed.
 
-| Argument        | Description                                                                                                                                                                                |
-| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `listKey`       | The key of the list being operated on.                                                                                                                                                     |
-| `operation`     | The CRUD operation being performed (`'create'`, `'read'`, `'update'`, `'delete'`).                                                                                                         |
-| `session`       | The current session object. See the [Sessions API](./session) for details.                                                                                                                 |
-| `originalInput` | For `create` and `update` operations, this is the value of `data` passed into the mutation. For `read` and `delete` operations this value is `undefined`.                                  |
-| `gqlName`       | The name of the query or mutation being called.                                                                                                                                            |
-| `itemId`        | The `id` of the item being updated/deleted in singular `update` and `delete` operations. The `id` of the item being searched for in a single item query. `undefined` for other operations. |
-| `itemIds`       | The `ids` of the items being updated/deleted in multiple `update` and `delete` operations. `undefined` for other operations.                                                               |
-| `context`       | The [`KeystoneContext`](./context) object of the originating GraphQL operation.                                                                                                            |
-
-> **Important**: When writing imperative access control functions it is essential to consider both singular and multi-value operations.
-> If you check the `itemId` in the singular case, then you also need to check the `itemIds` in the multi-value case.
-> Similarly, `originalInput` will be different in the singular and multi-valued cases.
+| Argument        | Description                                                                                                                                               |
+| --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `listKey`       | The key of the list being operated on.                                                                                                                    |
+| `operation`     | The CRUD operation being performed (`'create'`, `'read'`, `'update'`, `'delete'`).                                                                        |
+| `session`       | The current session object. See the [Sessions API](./session) for details.                                                                                |
+| `originalInput` | For `create` and `update` operations, this is the value of `data` passed into the mutation. For `read` and `delete` operations this value is `undefined`. |
+| `itemId`        | The `id` of the item being updated/deleted in `update` and `delete` operations. `undefined` for other operations.                                         |
+| `context`       | The [`KeystoneContext`](./context) object of the originating GraphQL operation.                                                                           |
 
 ```typescript
 import { config, createSchema, list } from '@keystone-next/keystone/schema';
@@ -174,9 +168,7 @@ export default config({
         operation,
         session,
         originalInput,
-        gqlName,
         itemId,
-        itemIds,
         context,
       }) => {
         return true;
@@ -298,7 +290,6 @@ Imperative access control functions are passed a collection of arguments which c
 | `operation`     | The CRU operation being performed (`'create'`, `'read'`, `'update'`).                                                                                              |
 | `session`       | The current session object. See the [Sessions API](./session) for details.                                                                                         |
 | `originalInput` | For `create` and `update` operations, this is the value of `data` passed into the mutation. For `read` operations this value is `undefined`.                       |
-| `gqlName`       | The name of the query or mutation being called.                                                                                                                    |
 | `context`       | The [`KeystoneContext`](./context) object of the originating GraphQL operation.                                                                                    |
 | `item`          | The item being updated, deleted, or read. This object is an unresolved list item. See the [list item API](./list-items) for more details on unresolved list items. |
 
@@ -318,7 +309,6 @@ export default config({
             operation,
             session,
             originalInput,
-            gqlName,
             context,
             item,
           }) => {

docs/pages/apis/context.mdx

@@ -44,10 +44,6 @@ context = {
   // Database access
   prisma,
 
-  // Access control helpers
-  getListAccessControlForUser,
-  getFieldAccessControlForUser,
-
   // Images API
   images: {
     getSrc,
@@ -62,7 +58,6 @@ context = {
 
   // Deprecated
   gqlNames,
-  keystone,
 };
 ```
 
@@ -123,11 +118,6 @@ The following functions will create a new `KeystoneContext` object with this beh
 
 The `KeystoneContext` object exposes the underlying database driver directly via `context.prisma`, which is a [Prisma Client](https://www.prisma.io/docs/reference/api-reference/prisma-client-reference) object.
 
-### Access control helpers
-
-The functions `getListAccessControlForUser()` and `getFieldAccessControlForUser()` are used by the internal Keystone resolvers to apply access control.
-They should not be called directly.
-
 ### Images API
 
 If [support for image fields](./config#images) is enabled in the system, then an `images` API will be made available on the `context` object.
@@ -171,6 +161,4 @@ They will be removed in future releases.
 
 `gqlNames`: A function which takes a `listKey` and returns an object containing the GraphQL query, mutation and type names related to that list.
 
-`keystone`: An object representing the internal state of the system.
-
 export default ({ children }) => <Markdown>{children}</Markdown>;

docs/pages/apis/fields.mdx

@@ -557,29 +557,27 @@ A `virtual` field represents a value which is computed a read time, rather than
 
 Options:
 
-- `resolver` (required):
-- `graphQLReturnType` (required):
+- `field` (required):
 - `graphQLReturnFragment` (default: `undefined` ):
-- `extendGraphQLTypes` (default: `[]`):
-- `args` (default: `[]`):
 
 ```typescript
 import { config, createSchema, list } from '@keystone-next/keystone/schema';
 import { virtual } from '@keystone-next/fields';
+import { schema } from '@keystone-next/types';
 
 export default config({
   lists: createSchema({
     ListName: list({
       fields: {
         fieldName: virtual({
-          resolver: (item, args, context, info) => `/* ... */`,
-          graphQLReturnType: '...',
+          field: schema.field({
+            type: schema.String,
+            args: { something: schema.arg({ type: schema.Int }) },
+            resolve(item, args, context, info) {
+
+            }
+          })
           graphQLReturnFragment: '...',
-          extendGraphQLTypes: ['...'],
-          args: [
-            { name: '...', type: 'String' },
-            /* ... */
-          ],
         }),
         /* ... */
       },

docs/pages/apis/schema.mdx

@@ -179,8 +179,7 @@ Options:
 
 - `description` (default: `undefined`): Sets the description of the associated GraphQL type in the generated GraphQL API documentation.
   Overrides the list-level `description` config option.
-- `itemQueryName` (default: List key, e.g `'User'`): Overrides the name used in singular mutations and queries (e.g. `User`, `updateUser`, etc).
-- `listQueryName`: (default: Pluralised list key, e.g. `'Users'`): Overrides the name used in multiple mutations and queries (e.g. `allUsers`, `updateUsers`, etc).
+- `plural`: (default: Pluralised list key, e.g. `'Users'`): Overrides the name used in multiple mutations and queries (e.g. `allUsers`, `updateUsers`, etc).
 - `queryLimits` (default: `undefined`): Allows you to limit the number of results returned from a query to this list in the GraphQL API.
   See also the global `graphql.queryLimits` option in the [System Configuration API](./config).
 - `cacheHint` (default: `undefined`): Allows you to specific the [dynamic cache control hints](https://www.apollographql.com/docs/apollo-server/performance/caching/#in-your-resolvers-dynamic) used for queries to this this list.