Remove references to deprecated directives (neo4j#11)

Co-authored-by: Lidia Zuin <[email protected]>

Author: darrellwarde

modules/ROOT/pages/directives/indexes-and-constraints.adoc

@@ -224,10 +224,7 @@ query {
 
 == Asserting constraints
 
-<<<<<<< HEAD
 In order to ensure that the specified constraints exist in the database, you need to run the function `assertIndexesAndConstraints` (see more details in xref::reference/api-reference/neo4jgraphql.adoc#api-reference-assertconstraints[API reference]).
-=======
->>>>>>> e36251b (fixing broken links)
 A simple example to create the necessary constraints might look like the following, assuming a valid driver instance in the variable `driver`. 
 This creates two constraints, one for each field decorated with `@id` and `@unique`, and apply the indexes specified in `@fulltext`:
 

modules/ROOT/pages/directives/reference.adoc

@@ -6,7 +6,7 @@
 
 The `@alias` directive will map a GraphQL schema field to a Neo4j property on a node or relationship.
 
-Reference: xref::reference/directives/database-mapping.adoc#type-definitions-alias[`@alias`]
+Reference: xref::/directives/database-mapping.adoc#type-definitions-alias[`@alias`]
 
 == `@coalesce`
 
@@ -116,6 +116,7 @@ The `@queryOptions` is to be used on nodes, where applied will inject values int
 
 Reference: xref::/directives/default-values.adoc#type-definitions-default-values-queryoptions[`@queryOptions`]
 
+<<<<<<< HEAD
 == `@readonly` label:deprecated[]
 
 This directive is deprecated. See the xref:/schema-configuration/field-configuration.adoc#_settable[`@settable`] directive.
@@ -124,6 +125,8 @@ The `@readonly` directive marks fields as read-only.
 Reference: xref::/schema-configuration/field-configuration.adoc#_readonly_deprecated[`@readonly`]
 >>>>>>> e36251b (fixing broken links)
 
+=======
+>>>>>>> dbb023b (Remove references to deprecated directives (#11))
 == `@relationship`
 
 The `@relationship` directive is used to configure relationships between object types.
@@ -170,6 +173,7 @@ Reference: xref::/directives/autogeneration.adoc#type-definitions-autogeneration
 
 The `@unique` directive indicates that there should be a uniqueness constraint in the database for the fields that it is applied to.
 
+<<<<<<< HEAD
 <<<<<<< HEAD
 Reference: xref::reference/type-definitions/indexes-and-constraints.adoc#type-definitions-constraints-unique[Unique node property constraints]
 =======
@@ -184,3 +188,6 @@ The `@writeonly` directive marks fields as write-only.
 
 Reference: xref::/schema-configuration/field-configuration.adoc#_writeonly_deprecated[`@writeonly`]
 >>>>>>> e36251b (fixing broken links)
+=======
+Reference: xref::reference/type-definitions/indexes-and-constraints.adoc#type-definitions-constraints-unique[Unique node property constraints]
+>>>>>>> dbb023b (Remove references to deprecated directives (#11))

modules/ROOT/pages/type-definitions/interfaces.adoc

@@ -6,7 +6,139 @@ This page describes how to use and define interfaces on relationship fields.
 
 == Creating an interface field
 
-Creating an interface field can be achieved through a mutation such as the following example, which adds an `Actor` and some productions they have acted in to the schema:
+The following schema defines a `Actor` type, that has a relationship `ACTED_IN`, of type `[Production!]!`. `Production` is an interface type with `Movie` and `Series` implementations. Note in this example that relationship properties have also been used with the `@relationshipProperties` directive, so that interfaces representing relationship properties can be easily distinguished.
+
+[source, graphql, indent=0]
+----
+interface Production {
+    title: String!
+    actors: [Actor!]!
+}
+
+type Movie implements Production {
+    title: String!
+    actors: [Actor!]! @relationship(type: "ACTED_IN", direction: IN, properties: "ActedIn")
+    runtime: Int!
+}
+
+type Series implements Production {
+    title: String!
+    actors: [Actor!]! @relationship(type: "ACTED_IN", direction: IN, properties: "ActedIn")
+    episodes: Int!
+}
+
+interface ActedIn @relationshipProperties {
+    role: String!
+}
+
+type Actor {
+    name: String!
+    actedIn: [Production!]! @relationship(type: "ACTED_IN", direction: OUT, properties: "ActedIn")
+}
+----
+
+These type definitions will be used for the rest of the examples in this chapter.
+
+=== Directive inheritance
+
+Any directives present on an interface or its fields will be "inherited" by any object types implementing it. For example, the type definitions above could be refactored to have the `@relationship` directive on the `actors` field in the `Production` interface instead of on each implementing type as it is currently:
+
+[source, graphql, indent=0]
+----
+interface Production {
+    title: String!
+    actors: [Actor!]! @relationship(type: "ACTED_IN", direction: IN, properties: "ActedIn")
+}
+
+type Movie implements Production {
+    title: String!
+    actors: [Actor!]!
+    runtime: Int!
+}
+
+type Series implements Production {
+    title: String!
+    actors: [Actor!]!
+    episodes: Int!
+}
+
+interface ActedIn @relationshipProperties {
+    role: String!
+}
+
+type Actor {
+    name: String!
+    actedIn: [Production!]! @relationship(type: "ACTED_IN", direction: OUT, properties: "ActedIn")
+}
+----
+
+[[type-definitions-interfaced-types-querying]]
+== Querying an interface
+
+Which implementations are returned by a query are dictated by the `where` filter applied.
+
+For example, the following will return all productions with title starting "The " for every actor:
+
+[source, graphql, indent=0]
+----
+query GetProductionsStartingWithThe {
+    actors {
+        name
+        actedIn(where: { node: { title_STARTS_WITH: "The " } }) {
+            title
+            ... on Movie {
+                runtime
+            }
+            ... on Series {
+                episodes
+            }
+        }
+    }
+}
+----
+
+Whilst the query below will only return the movies with title starting with "The " for each actor.
+
+[source, graphql, indent=0]
+----
+query GetMoviesStartingWithThe {
+    actors {
+        name
+        actedIn(where: { node: { _on: { Movie: { title_STARTS_WITH: "The " } } } }) {
+            title
+            ... on Movie {
+                runtime
+            }
+        }
+    }
+}
+----
+
+This is to prevent overfetching, and you can find an explanation of this xref::troubleshooting.adoc#appendix-preventing-overfetching[here].
+
+Alternatively, these implementation specific filters can be used to override filtering for a specific implementation. For example, if you wanted all productions with title starting with "The ", but movies with title starting with "A ", you could achieve this using the following:
+
+[source, graphql, indent=0]
+----
+query GetProductionsStartingWith {
+    actors {
+        name
+        actedIn(where: { node: { title_STARTS_WITH: "The ", _on: { Movie: { title_STARTS_WITH: "A " } } } }) {
+            title
+            ... on Movie {
+                runtime
+            }
+            ... on Series {
+                episodes
+            }
+        }
+    }
+}
+----
+
+== Creating using an interface field
+
+The below mutation creates an actor and some productions they've acted in:
 
 [source, graphql, indent=0]
 ----