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: modules/ROOT/pages/migration/index.adoc
+20-28Lines changed: 20 additions & 28 deletions
Original file line number
Diff line number
Diff line change
@@ -23,18 +23,11 @@ Here is a list of all the breaking changes from version 6.0.0 to 7.0.0.
23
23
24
24
=== Removed the `@unique` directive
25
25
26
-
The `@unique` directive is no longer supported:
27
-
28
-
[source, graphql, indent=0]
29
-
----
30
-
type Movie {
31
-
title: String! @unique
32
-
}
33
-
----
26
+
The `@unique` directive is no longer supported.
34
27
35
28
=== Removed implicit filtering fields
36
29
37
-
Implicit filtering fields have been removed. You must now use the explicit versions:
30
+
Implicit equality filtering fields have been removed. You must now use the dedicate input versions:
38
31
39
32
[cols="1,1"]
40
33
|===
@@ -128,20 +121,19 @@ a|
128
121
----
129
122
|===
130
123
131
-
The `deprecatedOptionsArgument` of `excludeDeprecatedFields` has been removed.
124
+
The `deprecatedOptionsArgument` option of `excludeDeprecatedFields` has been removed.
132
125
133
126
=== Removed the deprecated `directed` argument
134
127
135
128
The deprecated `directed` argument has been removed from queries. This argument previously allowed you to specify whether relationships should be directed or undirected at query time.
136
129
137
130
Please use the `queryDirection` argument of the `@relationship` directive instead.
138
131
139
-
The `directedArgument` setting of `excludeDeprecatedFields` has been removed.
132
+
The `directedArgument` option of `excludeDeprecatedFields` has been removed.
140
133
141
134
=== Accepted values of the `queryDirection` argument of `@relationship` has been changed
142
135
143
-
Following the removal of the `directed` argument,
144
-
the `queryDirection` argument of the `@relationship` directive now only accepts two possible values:
136
+
Following the removal of the `directed` argument, the `queryDirection` argument of the `@relationship` directive now only accepts two possible values:
145
137
146
138
- `DIRECTED` (default)
147
139
- `UNDIRECTED`
@@ -181,11 +173,11 @@ a|
181
173
----
182
174
|===
183
175
184
-
The `typename_IN` setting of `excludeDeprecatedFields` has been removed.
176
+
The `typename_IN` option of `excludeDeprecatedFields` has been removed.
185
177
186
178
=== Aggregations are no longer generated for `ID` fields
187
179
188
-
`ID` fields are excluded from aggregation fields and aggregation filters.
180
+
`ID` fields are excluded from aggregation selection sets and aggregation filters.
189
181
190
182
=== Single element relationships have been removed
191
183
@@ -211,15 +203,15 @@ type Movie @node {
211
203
----
212
204
|===
213
205
214
-
Single element relationships cannot be reliably enforced, leading to a data inconsistent with the schema. If the GraphQL model requires 1-1 relationships (such as in federations) these can now be achieved with the `@cypher` directive instead:
206
+
Single element relationships cannot be reliably enforced, leading to data inconsistent with the schema. If the GraphQL model requires 1-1 relationships (such as in federations) these can now be achieved with the `@cypher` directive instead:
215
207
216
208
[source, graphql, indent=0]
217
209
----
218
210
type Movie @node {
219
211
director: Person
220
212
@cypher(
221
213
statement: """
222
-
MATCH(this)-[:ACTED_IN]->(p:Person)
214
+
MATCH(this)-[:ACTED_IN]->(p:Person)
223
215
RETURN p
224
216
"""
225
217
columnName: "p"
@@ -261,7 +253,7 @@ The `connectOrCreate` operation has been removed due to limitations on its featu
261
253
262
254
=== Aggregate fields outside connection fields have been removed
263
255
264
-
Deprecated aggregate fields have been removed from the schema. Use aggregation fields within the connection fields instead.
256
+
Deprecated aggregate fields have been removed from the schema. Use aggregation fields within the connection selection set instead.
265
257
266
258
[cols="1,1"]
267
259
|===
@@ -291,11 +283,11 @@ query {
291
283
----
292
284
|===
293
285
294
-
The option `deprecatedAggregateOperations` has been removed from the `excludeDeprecatedFields` setting.
286
+
The `deprecatedAggregateOperations` option has been removed from the `excludeDeprecatedFields` setting.
295
287
296
288
=== Subscriptions are now opt-in
297
289
298
-
Subscriptions were automatically generated for all `@node` types.
290
+
Subscriptions are no longer automatically generated for all `@node` types.
299
291
300
292
In version 7.x, the `@subscription` directive is required to enable this functionality.
301
293
@@ -543,9 +535,9 @@ query {
543
535
544
536
The new form uses the Relay Cursor Connections Specification, which allows for pagination using cursors and access to the `pageInfo` field.
545
537
546
-
=== Removed implicit set operation
538
+
=== Removed implicit set operations
547
539
548
-
Implicit set operation in update mutations have been removed and the migration path involves two steps:
540
+
Implicit set operations in update mutations have been removed and the migration path involves two steps:
549
541
550
542
[cols="1,1"]
551
543
|===
@@ -581,7 +573,7 @@ mutation {
581
573
----
582
574
|===
583
575
584
-
The `implicitSet` argument of `excludeDeprecatedFields` has been removed.
576
+
The `implicitSet` option of `excludeDeprecatedFields` has been removed.
585
577
586
578
=== The Neo4j GraphQL Library and @neo4j/introspector now require Node.js 22 or greater
587
579
@@ -885,7 +877,7 @@ mutation {
885
877
----
886
878
|===
887
879
888
-
The `excludeDeprecatedFields` setting now contains the option `mutationOperations` to remove these deprecated operators:
880
+
The `excludeDeprecatedFields` option now contains the option `mutationOperations` to remove these deprecated operators:
889
881
890
882
[source, javascript, indent=0]
891
883
----
@@ -925,7 +917,7 @@ a|
925
917
----
926
918
|===
927
919
928
-
The `excludeDeprecatedFields` setting now contains the option `attributeFilters` to remove these deprecated filters:
920
+
The `excludeDeprecatedFields` option now contains the option `attributeFilters` to remove these deprecated filters:
929
921
930
922
[source, javascript, indent=0]
931
923
----
@@ -965,7 +957,7 @@ a|
965
957
----
966
958
|===
967
959
968
-
The `excludeDeprecatedFields` setting now contains the option `aggregationFiltersOutsideConnection` to remove these deprecated filters:
960
+
The `excludeDeprecatedFields` option now contains the option `aggregationFiltersOutsideConnection` to remove these deprecated filters:
969
961
970
962
[source, javascript, indent=0]
971
963
----
@@ -1011,7 +1003,7 @@ query Movies {
1011
1003
----
1012
1004
|===
1013
1005
1014
-
The `excludeDeprecatedFields` setting now contains the option `aggregationFilters` to remove these deprecated filters:
1006
+
The `excludeDeprecatedFields` option now contains the option `aggregationFilters` to remove these deprecated filters:
1015
1007
1016
1008
[source, javascript, indent=0]
1017
1009
----
@@ -1051,7 +1043,7 @@ a|
1051
1043
----
1052
1044
|===
1053
1045
1054
-
The `excludeDeprecatedFields` setting now contains the option `relationshipFilters` to remove these deprecated filters:
1046
+
The `excludeDeprecatedFields` option now contains the option `relationshipFilters` to remove these deprecated filters:
0 commit comments