Merge branch '5.x' into user-feedback-subscriptions-auth

Author: rsill-neo4j

.github/workflows/docs-pr-checks.yml

@@ -4,6 +4,7 @@ name: "Verify docs PR"
 on:
   pull_request:
     branches:
+      - 6.x
       - 5.x
       - 4.x
       - 3.x

.github/workflows/docs-teardown.yml

@@ -4,6 +4,7 @@ name: "Documentation Teardown"
 on:
   pull_request_target:
     branches:
+      - 6.x
       - 5.x
       - 4.x
       - 3.x

modules/ROOT/pages/deprecations.adoc

@@ -9,11 +9,11 @@ The following products and applications are deprecated:
 
 == GRANDstack starter app
 
-The main purpose of the GRANDstack starter app was to demonstrate how the Neo4j Labs GraphQL library could be used in the context of a full-stack application using React and Apollo client.
+The main purpose of the GRANDstack starter app was to demonstrate how the Neo4j Labs GraphQL Library could be used in the context of a full-stack application using React and Apollo client.
 It allowed developers to build applications more quickly and with a bigger focus on functionality, while also helping users who already had an existing frontend and needed a new back end.
 
 Over time, the GRANDstack starter app grew to support other frameworks such as Flutter and Angular, thus the need to revisit its scope.
-The intention is to replace this project with a new starter application product, which will focus on the back end and the configuration of the GraphQL library, as well as help developers with their frontend.
+The intention is to replace this project with a new starter application product, which will focus on the back end and the configuration of the GraphQL Library, as well as help developers with their frontend.
 
 In the meantime, the `create-grandstack-app` npm package has been marked as deprecated.
 It can still be used to skeleton a GRANDstack app, but the user will be warned that the package is deprecated.

modules/ROOT/pages/mutations/create.adoc

@@ -112,7 +112,7 @@ Read about xref:mutations/update.adoc#_connectorcreate_relationships[`update`] f
 
 == `connectOrCreate` relationships
 
-If a related node has the `@unique` directive defined, you can use `connectOrCreate` nested in a `CREATE` mutation to perform an operation similar to a link:https://neo4j.com/docs/cypher-manual/current/clauses/merge/[Cypher `MERGE`] operation on the related node.
+If a related node has the `@unique` directive defined, you can use `connectOrCreate` nested in a `create` mutation to perform an operation similar to a link:https://neo4j.com/docs/cypher-manual/current/clauses/merge/[Cypher `MERGE`] operation on the related node.
 This will create a new relationship and the related node if it doesn't exist yet.
 
 Consider the following type definitions:
@@ -157,9 +157,9 @@ This ensures that a movie with ID 1234 exists and is connected to `"Tom Hanks"`.
 If the movie does not exist, it will be created with the title `"Forrest Gump"`.
 If a movie with the given ID already exists, it will also be connected to `"Tom Hanks"`, and keep whatever title it has.
 
-== `CREATE` optimization
+== `create` optimization
 
-With `CREATE` operations, there is no limit on how many nodes can be created at once.
+With `create` operations, there is no limit on how many nodes can be created at once.
 However, there is a known performance issue for large batch sizes. 
 
 The Neo4j GraphQL Library contains an optimization feature designed to mitigate it, but it does not work in the following scenarios:

modules/ROOT/pages/mutations/delete.adoc

@@ -72,43 +72,4 @@ mutation {
     relationshipsDeleted
   }
 }
-----
-
-This query is equivalent to:
-
-[source, graphql, indent=0]
-----
-mutation {
-    deleteUsers(
-        where: {
-            name: "Jane Doe"
-        },
-        delete: {
-            posts: [
-                where: {
-                    node: {
-                        creator: {
-                            name: "Jane Doe"
-                        }
-                    }
-                }
-            ]
-        }
-    ) {
-        nodesDeleted
-        relationshipsDeleted
-    }
-}
-----
-
-Note that the output Cypher statement should also have a redundant `WHERE` clause:
-
-// !
-//Please add the cypher statement:
-
-//[source, cypher, indent=0]
-//----
-//DELETE User (name:"Jane Doe") 
-//WHERE Posts -
-//----
-// !
+----

modules/ROOT/pages/mutations/update.adoc

@@ -398,56 +398,6 @@ a|
 |===
 ====
 
-=== Mixing `_PUSH` and `_POP`
-
-It is possible to perform both a `_PUSH` and `_POP` operation in one single `update` mutation.
-
-Consider the following type definitions:
-
-[source, graphql, indent=0]
-----
-type Movie {
-    title: String
-    tags: [String]
-    moreTags: [String]
-}
-----
-
-You can update both property arrays with either `_PUSH` or `_POP` operators at once:
-
-.Mutation with both a `_PUSH` and a `_POP`
-====
-[source, graphql, indent=0]
-----
-mutation {
-    updateMovies (update: { tags_POP: 1, moreTags_PUSH: "a different tag" }) {
-        movies {
-            title
-            tags
-            moreTags
-        }
-    }
-}
-----
-
-[col=1,1]
-|===
-| Before | After
-
-a|
-```
-    tags: ['some tag']
-    moreTags: []
-```
-
-a|
-```
-    tags: []
-    moreTags ['a different tag']
-```
-|===
-====
-
 == Mathematical operators
 
 You can use mathematical operators to update numerical fields based on their original values in a single DB transaction.

modules/ROOT/pages/queries-aggregations/filtering.adoc

@@ -440,7 +440,7 @@ query {
 
 == Aggregation filtering
 
-The Neo4j GraphQL library offers an aggregation key inside the `where` argument of each relationship. 
+The Neo4j GraphQL Library offers an aggregation key inside the `where` argument of each relationship. 
 You can use it both on the `node` and `edge` of a relationship.
 
 Here are some examples on how to apply this kind of filtering: