Skip to content

Commit f4d6dee

Browse files
Geoffroy Empainjohnbiundo
andauthored
Update content/graphql/guards-interceptors.md
Co-Authored-By: John Biundo <[email protected]>
1 parent c6be316 commit f4d6dee

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/graphql/guards-interceptors.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ async upvotePost(
8686

8787
> info **Hint** In the above example, we have assumed that the `user` object is assigned to the context of your GraphQL application.
8888
89-
#### Interceptors at the `@ResolveField()` method level
89+
#### Execute enhancers at the field/method level
9090

9191
In a GraphQL context, interceptors [do not access the full GraphQL response](https://github.com/nestjs/graphql/issues/320#issuecomment-511193229): they only get the response of the `@Query()`/`@Mutation()` method, but not the complete response with the resolved fields. You can tell Nest to execute interceptors (as well as guards and filters) for methods annotated `@ResolveField()` by setting the `fieldResolverEnhancers` option in `GqlModuleOptions`:
9292

0 commit comments

Comments
 (0)