From cb9d7d32c8180c600254b965f74910f7fe77e561 Mon Sep 17 00:00:00 2001 From: Dainis <44690511+dgrinbergs@users.noreply.github.com> Date: Sat, 7 Jun 2025 22:18:36 +0100 Subject: [PATCH] fixed typo in controllers.adoc Signed-off-by: Dainis <44690511+dgrinbergs@users.noreply.github.com> --- spring-graphql-docs/modules/ROOT/pages/controllers.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spring-graphql-docs/modules/ROOT/pages/controllers.adoc b/spring-graphql-docs/modules/ROOT/pages/controllers.adoc index 269c1978..7ed593c9 100644 --- a/spring-graphql-docs/modules/ROOT/pages/controllers.adoc +++ b/spring-graphql-docs/modules/ROOT/pages/controllers.adoc @@ -975,7 +975,7 @@ Supported return types are listed below: == Namespacing At the schema level, query and mutation operations are defined directly under the `Query` and `Mutation` types. -Rich GraphQL APIs can define dozens of operation sunder those types, making it harder to explore the API and separate concerns. +Rich GraphQL APIs can define dozens of operations under those types, making it harder to explore the API and separate concerns. You can choose to https://www.apollographql.com/docs/technotes/TN0012-namespacing-by-separation-of-concern/[define Namespaces in your GraphQL schema]. While there are some caveats with this approach, you can implement this pattern with Spring for GraphQL annotated controllers.