Remove the mongoose adapter (#5280)

.changeset/real-ears-cheat.md

@@ -1,6 +1,5 @@
 ---
 '@keystone-next/fields': major
-'@keystone-next/adapter-mongoose-legacy': major
 '@keystone-next/fields-legacy': major
 ---
 

.changeset/tame-points-provide.md

@@ -0,0 +1,13 @@
+---
+'@keystone-next/example-ecommerce': patch
+'@keystone-next/example-roles': patch
+'@keystone-next/admin-ui': patch
+'@keystone-next/fields': patch
+'@keystone-next/keystone': patch
+'@keystone-next/fields-legacy': patch
+'@keystone-next/test-utils-legacy': patch
+'@keystone-next/api-tests-legacy': patch
+'@keystone-next/benchmarks-legacy': patch
+---
+
+Removed the `adapters-mongoose-legacy` packages dependency.

CONTRIBUTING.md

@@ -57,11 +57,11 @@ While not every changeset is going to need a huge amount of detail, a good idea
 - WHY the change was made
 - HOW a consumer should update their code
 
-An example, if you generate a changeset that includes `adapter-mongoose` as a patch, and `keystone` as a minor, you can merge your PR, and the next time the `version-packages` command is run, these will both be updated.
+An example, if you generate a changeset that includes `adapter-prisma` as a patch, and `keystone` as a minor, you can merge your PR, and the next time the `version-packages` command is run, these will both be updated.
 
 ```md
 ---
-'@keystone-next/adapter-mongoose-legacy': patch
+'@keystone-next/adapter-prisma-legacy': patch
 '@keystone-next/keystone-legacy': minor
 ---
 

STYLE_GUIDE.md

@@ -33,7 +33,7 @@ Also, it should go without saying:
 
 - Ensure correct spelling; spell-check documents before committing.
   (We _favour_ UK/Australian spelling.)
-- Ensure correct capitalisation, inc. product names and acronyms (eg: JavaScript, URL, Node.js, MongoDB).
+- Ensure correct capitalisation, inc. product names and acronyms (eg: JavaScript, URL, Node.js).
   Note, _abbreviations_ like "etc.", "ie." and "eg." are not acronyms;
   they should only be capitalised if at the start of a sentence.
 - Ensure correct English grammar (or Miss Willings will come for you 👩🏼‍🏫).

examples-next/README.md

@@ -12,7 +12,6 @@ To run the projects locally:
 
 - Clone this repo
 - Run `yarn` in the root (this repo is a monorepo and uses yarn workspaces, so that will install everything you'll need)
-- Make sure you have a local mongo server up and running on the default port
 - Open one of the example project folders in your terminal and run `yarn dev`
 
 If everything works 🤞 the GraphQL Server and Admin UI will start on [localhost:3000](http://localhost:3000)

examples-next/ecommerce/README.md

@@ -14,7 +14,6 @@ To run the project locally:
 
 - Clone this repo
 - Run `yarn` in the root (this repo is a monorepo and uses yarn workspaces, so that will install everything you'll need)
-- Make sure you have a local mongo server up and running on the default port
 - Open this folder in your terminal and run `yarn dev`
 
 If everything works 🤞 the GraphQL Server and Admin UI will start on [localhost:3000](http://localhost:3000)

examples-next/roles/README.md

@@ -16,7 +16,6 @@ To run the project locally:
 
 - Clone this repo
 - Run `yarn` in the root (this repo is a monorepo and uses yarn workspaces, so that will install everything you'll need)
-- Make sure you have a local mongo server up and running on the default port
 - Open this folder in your terminal and run `yarn dev`
 
 If everything works 🤞 the GraphQL Server and Admin UI will start on [localhost:3000](http://localhost:3000)

packages-next/admin-ui/TODO.md

@@ -12,7 +12,6 @@
 - [ ] Add an example that implements custom fields
 - [x] `idField` option
   - [x] autoIncrement in fields package
-  - [x] mongoId in fields package
   - [x] `idField` option
   - [x] disallow `id` field in fields object
   - [x] default `idField` to `autoIncrement` for Prisma with fieldMode: 'hidden' for itemView and createView

packages-next/fields/src/types/autoIncrement/tests/test-fixtures.ts

@@ -15,8 +15,7 @@ export const fieldName = 'orderNumber';
 export const skipCreateTest = false;
 export const skipUpdateTest = true;
 
-// `AutoIncrement` field type is not supported by `mongoose`. So, we need to filter it out while performing `API` tests.
-export const unSupportedAdapterList = ['mongoose', 'prisma_sqlite'];
+export const unSupportedAdapterList = ['prisma_sqlite'];
 
 // Be default, `AutoIncrement` are read-only. But for `isRequired` test purpose, we need to bypass these restrictions.
 export const fieldConfig = (matrixValue: MatrixValue) => ({

packages-next/keystone/package.json

@@ -27,7 +27,6 @@
     "@types/express": "^4.17.11",
     "@types/fs-extra": "^9.0.9",
     "@types/graphql-upload": "^8.0.4",
-    "@types/keystonejs__adapter-mongoose": "^5.1.2",
     "@types/keystonejs__keystone": "^7.0.1",
     "@types/pluralize": "^0.0.29",
     "@types/prettier": "^2.2.3",