You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: readme.adoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -308,7 +308,7 @@ The literal values are turned into Cypher query parameters.
308
308
=== Handle Relationships via @relation Directive on Schema Fields
309
309
310
310
If you want to represent a relationship from the graph in GraphQL you have to add a `@relation` directive which contains the relationship-type and the direction.
311
-
The default relationship-type is 'OUT'.
311
+
The default direction for a relationship is 'OUT'. Other values are 'IN' and 'BOTH'.
312
312
So you can use different domain names in your GraphQL fields that are independent of your graph model.
313
313
314
314
[source,graphql]
@@ -465,7 +465,7 @@ ORDER BY person.name ASC, person.age DESC
465
465
466
466
NOTE: We don't yet support ordering on nested relationship fields.
467
467
468
-
=== @relationship on Types
468
+
=== Handle Rich Relationships via @relation Directive on Schema Types
469
469
470
470
To represent rich relationship types with properties, a `@relation` directive is supported on an object type.
0 commit comments