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: content/blog/deep-dive-merged-fields.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -214,7 +214,7 @@ The second thing to keep in mind is that different directives can be on each fie
214
214
215
215
So if you want to know all directives for the current field you are resolving you actually need to look at all of the merged fields from the query.
216
216
217
-
# Merged fields in graphql-js and GraphQl Java
217
+
# Merged fields in graphql-js and GraphQL Java
218
218
219
219
In graphql-js merged fields are relevant when you implement a resolver and you need access to the specific ast field of the query. The `info` objects has a property `fieldNodes` which gives you access to all ast fields which are merged together.
0 commit comments