apply v7 migration on types folder

Author: MacondoExpress

modules/ROOT/pages/types/interfaces.adoc

@@ -31,7 +31,7 @@ type Series implements Production @node {
 }
 
 type ActedIn @relationshipProperties {
-    role: String!
+    role: String
 }
 
 type Actor @node {
@@ -52,7 +52,7 @@ The following will return all productions with title starting "The " for every a
 query GetProductionsStartingWithThe {
     actors {
         name
-        actedIn(where: { node: { title_STARTS_WITH: "The " } }) {
+        actedIn(where: { node: { title: { startsWith: "The " } } }) {
             title
             ... on Movie {
                 runtime
@@ -65,14 +65,14 @@ query GetProductionsStartingWithThe {
 }
 ----
 
-The following query will only return the movies with title starting with "The " for each actor by filtering them by `typename_IN`:
+The following query will only return the movies with title starting with "The " for each actor by filtering them by `typename`:
 
 [source, graphql, indent=0]
 ----
 query GetMoviesStartingWithThe {
     actors {
         name
-        actedIn(where: { node: { title_STARTS_WITH: "The ", typename_IN: [Movie]  } }) {
+        actedIn(where: { node: { title: { startsWith: "The " }, typename: [Movie]  } }) {
             title
             ... on Movie {
                 runtime
@@ -151,22 +151,26 @@ Take the following example:
 [source, graphql, indent=0]
 ----
 mutation CreateActorAndProductions {
-    updateActors(
-        where: { name_EQ: "Woody Harrelson" }
+  updateActors(
+    where: { name: { eq: "Woody Harrelson" } }
+    update: {
+      actedIn: {
         connect: {
-            actedIn: {
-                where: { node: { title_EQ: "Zombieland" } }
-                connect: { actors: { where: { node: { name_EQ: "Emma Stone" } } } }
-            }
-        }
-    ) {
-        actors {
-            name
-            actedIn {
-                title
-            }
+          where: { node: { title: { eq: "Zombieland" } } }
+          connect: {
+            actors: { where: { node: { name: { eq: "Emma Stone" } } } }
+          }
         }
+      }
+    }
+  ) {
+    actors {
+      name
+      actedIn {
+        title
+      }
     }
+  }
 }
 ----
 
@@ -185,17 +189,17 @@ For example, the following query returns all productions (`movies` and `series`)
 [source, graphql, indent=0]
 ----
 query GetProductionsStartingWithThe {
-    actors {
-        name
-        actedIn(where: { node: { title_STARTS_WITH: "The " } }) {
-            title
-            ... on Movie {
-                runtime
-            }
-            ... on Series {
-                episodes
-            }
-        }
+  actors {
+    name
+    actedIn(where: { title: { startsWith: "The " } }) {
+      title
+      ... on Movie {
+        runtime
+      }
+      ... on Series {
+        episodes
+      }
     }
+  }
 }
 ----

modules/ROOT/pages/types/relationships.adoc

@@ -45,19 +45,23 @@ type Movie @node {
     title: String!
     released: Int!
     actors: [Person!]! @relationship(type: "ACTED_IN", direction: IN)
-    director: Person! @relationship(type: "DIRECTED", direction: IN)
+    directors: [Person!]! @relationship(type: "DIRECTED", direction: IN)
 }
 ----
 
 Note that, in this query:
 
 * A `Person` can _act in_ or _direct_ multiple movies, and a `Movie` can have multiple actors. 
-However, it is rare for a `Movie` to have more than one director, so you can model this cardinality in your type definitions, to ensure accuracy of your data.
-* A `Movie` isn't really a `Movie` without a director, and this has been signified by marking the `director` field as non-nullable.
-This means that a `Movie` *must* have a `DIRECTED` relationship coming into it to be valid.
+  While it is rare for a `Movie` to have more than one director, Neo4j GraphQL Library requires all relationships to be modeled as "many" relationships (using arrays).
+* Even conceptually one-to-one relationships like a movie having a single director must be represented as arrays (e.g., `directors: [Person!]!`) because Neo4j cannot reliably enforce 1:1 cardinality between nodes.
 * To figure out whether the `direction` argument of the `@relationship` directive should be `IN` or `OUT`, visualize your relationships like in the diagram above, then model out the direction of the arrows.
 * The `@relationship` directive is a reference to Neo4j relationships, whereas in the schema, the phrase `edge(s)` is used to be consistent with the general API language used by Relay.
 
+=== Neo4j GraphQL Cardinality Limitation
+
+It's important to understand that Neo4j cannot reliably enforce 1:1 cardinality between nodes in a graph database. Therefore, all relationships in Neo4j GraphQL are modeled as "many" relationships (using arrays) even when conceptually they represent one-to-one relationships.
+As alternative you can define your relationship with the `@cypher` directive, however some of the functionality provided by the Neo4j GraphQL Library will not be available.
+
 === Relationship properties
 
 You can add relationship properties to the example in two steps:
@@ -83,7 +87,7 @@ type Movie @node {
     title: String!
     released: Int!
     actors: [Person!]! @relationship(type: "ACTED_IN", properties: "ActedIn", direction: IN)
-    director: Person! @relationship(type: "DIRECTED", direction: IN)
+    directors: [Person!]! @relationship(type: "DIRECTED", direction: IN)
 }
 
 type ActedIn @relationshipProperties {
@@ -142,7 +146,6 @@ type Person @node {
 ----
 
 `queryDirection` can have the following values:
-
 * `DIRECTED`: only directed queries can be performed on this relationship.
 * `UNDIRECTED`: only undirected queries can be performed on this relationship.
 
@@ -160,20 +163,20 @@ mutation CreateMovieAndDirector {
         {
             title: "Forrest Gump"
             released: 1994
-            director: {
-                create: {
+            directors: {
+                create: [{
                     node: {
                         name: "Robert Zemeckis"
                         born: 1951
                     }
-                }
+                }]
             }
         }
     ]) {
         movies {
             title
             released
-            director {
+            directors {
                 name
                 born
             }
@@ -187,40 +190,40 @@ You then need to create the actor in this example, and connect them to the new `
 [source, graphql, indent=0]
 ----
 mutation CreateActor {
-    createPeople(input: [
-        {
-            name: "Tom Hanks"
-            born: 1956
-            actedInMovies: {
-                connect: {
-                    where: {
-                        node: { title_EQ: "Forrest Gump" }
-                    }
-                    edge: {
-                        roles: ["Forrest"]
-                    }
-                }
-            }
+  createPeople(
+    input: [
+      {
+        name: "Tom Hanks"
+        born: 1956
+        actedInMovies: {
+          connect: {
+            where: { node: { title: { eq: "Forrest Gump" } } }
+            edge: { roles: ["Forrest"] }
+          }
         }
-    ]) {
-        movies {
-            title
-            released
-            director {
-                name
-                born
+      }
+    ]
+  ) {
+    people {
+      name
+      born
+      actedInMovies {
+        title
+        released
+        actorsConnection {
+          edges {
+            properties {
+              roles
             }
-            actorsConnection {
-                edges {
-                    roles
-                    node {
-                        name
-                        born
-                    }
-                }
+            node {
+              name
+              born
             }
+          }
         }
+      }
     }
+  }
 }
 ----
 
@@ -236,7 +239,7 @@ mutation CreateMovieDirectorAndActor {
         {
             title: "Forrest Gump"
             released: 1994
-            director: {
+            directors: {
                 create: {
                     node: {
                         name: "Robert Zemeckis"
@@ -262,13 +265,15 @@ mutation CreateMovieDirectorAndActor {
         movies {
             title
             released
-            director {
+            directors {
                 name
                 born
             }
             actorsConnection {
                 edges {
-                    roles
+                    properties {
+                      roles
+                    }
                     node {
                         name
                         born
@@ -289,16 +294,18 @@ Now that you have the `Movie` information in your database, you can query everyt
 [source, graphql, indent=0]
 ----
 query {
-    movies(where: { title_EQ: "Forrest Gump" }) {
+    movies(where: { title: { eq: "Forrest Gump" } }) {
         title
         released
-        director {
+        directors {
             name
             born
         }
         actorsConnection {
             edges {
-                roles
+                properties {
+                    roles
+                }
                 node {
                     name
                     born

modules/ROOT/pages/types/scalar.adoc

@@ -38,7 +38,7 @@ a|
 [source, graphql, indent=0]
 ----
 query {
-    files(where: { size_EQ: 9223372036854775807 }) {
+    files(where: { size: { eq: 9223372036854775807 }}) {
         size
     }
 }

modules/ROOT/pages/types/unions.adoc

@@ -96,7 +96,7 @@ While this particular query only returns blogs, you could for instance use a fil
 query GetUsersWithAllContent {
     users {
         name
-        content(where: { Blog: { NOT: { title_EQ: null } }}) {
+        content(where: { Blog: { NOT: { title: { eq: null } } }}) {
             ... on Blog {
                 title
             }