Skip to content

Update Reactive DataFetcher anchor id #1530

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bclozel merged 1 commit into from
Sep 21, 2026
+5 −5
Merged

Update Reactive DataFetcher anchor id #1530

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions spring-graphql-docs/modules/ROOT/pages/controllers.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,7 @@ for fields under the Query, Mutation, and Subscription types respectively. For e
----

`@SchemaMapping` handler methods have flexible signatures and can choose from a range of
method arguments and return values..
method arguments and return values.


[[controllers.schema-mapping.signature]]
Expand Down Expand Up @@ -224,7 +224,7 @@ Schema mapping handler methods can return:
| `Mono<T>` and `Flux<T>`
| For asynchronous value(s).

Supported for controller methods and for any `DataFetcher` as described in xref:request-execution.adoc#execution.reactive-datafetcher[Reactive `DataFetcher`].
Supported for controller methods and for any `DataFetcher` as described in xref:request-execution.adoc#execution.reactivedatafetcher[Reactive `DataFetcher`].

| Kotlin `suspend fun` and `Flow`
| They are automatically adapted to `Mono` and `Flux`.
Expand Down
6 changes: 3 additions & 3 deletions spring-graphql-docs/modules/ROOT/pages/request-execution.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -411,7 +411,7 @@ execution to complete more quickly.

Spring for GraphQL supports:

- <<execution.reactive-datafetcher, Reactive data fetchers>>, and those are
- <<execution.reactivedatafetcher, Reactive data fetchers>>, and those are
adapted to `CompletionStage` as expected by `AsyncExecutionStrategy`.
- `CompletionStage` as return value.
- Controller methods that are Kotlin coroutine methods.
Expand Down Expand Up @@ -533,7 +533,7 @@ automatically through the `java.util.ServiceLoader` mechanism.
[[execution.context.webflux]]
=== WebFlux

A xref:request-execution.adoc#execution.reactive-datafetcher[Reactive `DataFetcher`] can rely on access to Reactor context that
A xref:request-execution.adoc#execution.reactivedatafetcher[Reactive `DataFetcher`] can rely on access to Reactor context that
originates from the WebFlux request handling chain. This includes Reactor context
added by xref:transports.adoc#server.interception[WebGraphQlInterceptor] components.

Expand Down Expand Up @@ -717,7 +717,7 @@ GraphQlSource.schemaResourceBuilder()
<1> Create type visitor with one or more ``ConnectionAdapter``s.
<2> Resister the type visitor.

There are built-in xref:data.adoc#data.pagination.scroll[built-in] ``ConnectionAdapter``s
There are xref:data.adoc#data.pagination.scroll[built-in] ``ConnectionAdapter``s
for Spring Data's `Window` and `Slice`. You can also create your own custom adapter.
`ConnectionAdapter` implementations rely on a
xref:request-execution.adoc#execution.pagination.cursor.strategy[`CursorStrategy`] to
Expand Down
Loading