From 8d9d4ecb1cbd93d1ff0bc5dfebc2276a96df1ce4 Mon Sep 17 00:00:00 2001 From: Oryan Date: Mon, 26 Oct 2026 09:12:24 -0400 Subject: [PATCH] Link the How graphql-java-tools builds a schema wiki page from the README --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 03f7126a..122b389f 100644 --- a/README.md +++ b/README.md @@ -60,7 +60,7 @@ Take a look at our [documentation](https://graphql-java-kickstart.github.io/tool A few libraries exist to ease the boilerplate pain, including [GraphQL-Java's built-in schema-first wiring](https://www.graphql-java.com/documentation/master/schema/), but none (so far) do type and datafetcher discovery. * **Stateful Data Fetchers**: If you're using an IOC container (like Spring), it's hard to wire up datafetchers that make use of beans you've already defined without a bunch of fragile configuration. GraphQL Java Tools allows you to register "Resolvers" for any type that can bring state along and use that to resolve fields. * **Generated DataFetchers**: GraphQL Java Tools automatically creates data fetchers for your fields that call the appropriate method on your java class. This means all you have to do to create a new field is add the field definition to your schema and add a corresponding method on your class. -* **Type->Class Discovery**: GraphQL Java Tools starts from your root objects (Query, Mutation) and, as it's generating data fetchers for you, starts to learn about the classes you use for a certain GraphQL type. +* **Type->Class Discovery**: GraphQL Java Tools starts from your root objects (Query, Mutation) and, as it's generating data fetchers for you, starts to learn about the classes you use for a certain GraphQL type. [How graphql-java-tools builds a schema](https://github.com/graphql-java-kickstart/graphql-java-tools/wiki/How-graphql-java-tools-builds-a-schema) walks through each step. * **Class Validation**: Since there aren't any compile-time checks of the type->class relationship, GraphQL Java Tools will warn you if you provide classes/types that you don't need to, as well as erroring if you use the wrong Java class for a certain GraphQL type when it builds the schema. * **Unit Testing**: Since your GraphQL schema is independent of your data model, this makes your classes simple and extremely testable.