rename keystone folder to core (keystonejs#7252)

* rename keystone folder to core

* update repository field

* fix path name in prisma utils

* replace anywhere that uses packages/keystone

CONTRIBUTING.md

@@ -275,7 +275,7 @@ Now, for each release we want to backport to, we follow this process:
    (\
    export PACKAGE_NAME=@keystonejs/keystone && \
    export OTP_CODE= && \
-   cd packages/keystone && \
+   cd packages/core && \
    yarn publish --tag=backport --otp=$OTP_CODE && \
    export BACKPORTED_VERSION=`npm dist-tag ls $PACKAGE_NAME | grep 'backport' | sed -e 's/backport: //'` && \
    yarn tag remove $PACKAGE_NAME backport --otp=$OTP_CODE && \

STYLE_GUIDE.md

@@ -118,8 +118,8 @@ For links to work across these mediums, certain rules for URLs formulation must
   - The full filename, include the extension
     - Eg. `/docs/pages/guides/cli.mdx` (**not** `/docs/guides/cli`)
 - Links to `README.md` files must be explicit; they cannot rely on the GitHub behaviour that uses `README.md` at a sort of "index" for a directory
-  - Eg. `/packages/keystone/README.md#CLI` (**not** `/packages/keystone#CLI`)
-- Links to directories end in a slash (eg. `/packages/keystone/`)
+  - Eg. `/packages/core/README.md#CLI` (**not** `/packages/core#CLI`)
+- Links to directories end in a slash (eg. `/packages/core/`)
   - This as is convention for URLs (so as not to be confused with a files)
 
 ## Code and Code Blocks

docs/pages/docs/guides/custom-fields.mdx

@@ -14,9 +14,9 @@ There are two parts to a field type:
 - The **frontend** portion which defines how the field looks and behaves in the Admin UI.
 
 The general approach to creating a custom field type is to take an existing field type and make the appropriate changes for your use case.
-In this guide we're going to create a field type `myInt` which recreates the [`integer`](https://github.com/keystonejs/keystone/tree/main/packages/keystone/src/fields/types/integer) field type.
+In this guide we're going to create a field type `myInt` which recreates the [`integer`](https://github.com/keystonejs/keystone/tree/main/packages/core/src/fields/types/integer) field type.
 
-!> For inspiration, see [the source for the fields that Keystone provides](https://github.com/keystonejs/keystone/tree/main/packages/keystone/src/fields/types) and the [Custom Fields](https://github.com/keystonejs/keystone/tree/main/examples/custom-field) example project.
+!> For inspiration, see [the source for the fields that Keystone provides](https://github.com/keystonejs/keystone/tree/main/packages/core/src/fields/types) and the [Custom Fields](https://github.com/keystonejs/keystone/tree/main/examples/custom-field) example project.
 
 ## Backend
 

examples/custom-field/stars-field/index.ts

@@ -11,7 +11,7 @@ import { graphql } from '@keystone-6/core';
 // this field is based on the integer field
 // but with validation to ensure the value is within an expected range
 // and a different input in the Admin UI
-// https://github.com/keystonejs/keystone/tree/main/packages/keystone/src/fields/types/integer
+// https://github.com/keystonejs/keystone/tree/main/packages/core/src/fields/types/integer
 
 export type StarsFieldConfig<ListTypeInfo extends BaseListTypeInfo> =
   CommonFieldConfig<ListTypeInfo> & {

package.json

@@ -151,7 +151,7 @@
       "packages/**/*.{js,ts,tsx}",
       "!**/*.d.ts",
       "!packages/**/dist/**",
-      "!packages/keystone/src/fields/**/test-fixtures.{js,ts}"
+      "!packages/core/src/fields/**/test-fixtures.{js,ts}"
     ]
   },
   "resolutions": {

packages/keystone/package.json → packages/core/package.json

@@ -163,5 +163,5 @@
       "types/index.ts"
     ]
   },
-  "repository": "https://github.com/keystonejs/keystone/tree/main/packages/keystone"
+  "repository": "https://github.com/keystonejs/keystone/tree/main/packages/core"
 }

packages/keystone/src/types/core.ts → packages/core/src/types/core.ts

@@ -37,7 +37,7 @@ export type GraphQLSchemaExtension<Context extends KeystoneContext> = {
   resolvers: Record<string, Record<string, GraphQLResolver<Context>>>;
 };
 
-// TODO: don't duplicate this between here and packages/keystone/ListTypes/list.js
+// TODO: don't duplicate this between here and packages/core/ListTypes/list.js
 export function getGqlNames({
   listKey,
   pluralGraphQLName,

prisma-utils/src/index.ts

@@ -106,7 +106,7 @@ ${
         2
       )
     );
-    const filepath = `${__dirname}/../../packages/keystone/src/types/filters/providers/${provider}.ts`;
+    const filepath = `${__dirname}/../../packages/core/src/types/filters/providers/${provider}.ts`;
     const newContent = format(
       `// Do not manually modify this file, it is automatically generated by the package at /prisma-utils in this repo.
 // Update the script if you need this file to be different