Skip to content

Commit 0006321

Browse files
Apply suggestions from code review
Co-authored-by: Darrell Warde <[email protected]>
1 parent 21a6c03 commit 0006321

File tree

1 file changed

+3
-3
lines changed
  • docs/modules/ROOT/pages/guides/v4-migration

1 file changed

+3
-3
lines changed

docs/modules/ROOT/pages/guides/v4-migration/index.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -122,9 +122,9 @@ new Neo4jGraphQL({
122122
==== `requires` changes
123123

124124
In version 4.0.0, it is now possible to require non-scalar fields. This means it is also possible to require fields on related type.
125-
To make this possible, the `requires` argument now accept a graphql selection set instead of a list of strings.
125+
To make this possible, the `requires` argument now accept a GraphQL selection set instead of a list of strings.
126126

127-
Therefore, the following type definitions:
127+
Therefore, given the following type definitions in 3.0.0:
128128

129129
[source, graphql, indent=0]
130130
----
@@ -135,7 +135,7 @@ type User {
135135
}
136136
----
137137

138-
Would need to be modified to use a selection set as below:
138+
In 4.0.0, these need to be modified to use a selection set as below:
139139

140140
[source, graphql, indent=0]
141141
----

0 commit comments

Comments
 (0)