Migration guide available to migrate from 5,x,x to 6.x.x / Schemas do not get discovered anymore on 6.x.x

[majoko87]

Hey there,
Is there any migration guide available to migrate from 5,x,x to 6.x.x?

I noticed that the package name has changed from com.coxautodev.graphql to graphql.kickstart
Further: after changing the version and the package imports it seems that the schema files *.graphqls do not get discovered anymore. Before the change to 6.x.x every *.graphqls file was discovered correctly and the query and mutation "endpoints" were available. After the change it seems that the schema files do not get resolved anymore. That leads to the problem that no mutation or query is available anymore.

PS:
Is there any real world example available for the DataLoader / BatchLoader?
Thanks!

[anoop4tech]

facing the same issue with graphql-java-tools version (6.0.0) and graphiql-spring-boot-starter version (6.0.1), schema no longer discoverable.

[vojtapol]

Please include your pom.xml or build.gradle files. You can leave out everything except any GraphQL dependencies.

GrpahQL Java Tools does not discover schema files automatically.

[majoko87]

@vojtapol do they not? I thought so.
Before the version update

 <dependency>
            <groupId>com.graphql-java-kickstart</groupId>
            <artifactId>graphql-spring-boot-starter</artifactId>
            <version>5.10.0</version>
        </dependency>
        <dependency>
            <groupId>com.graphql-java-kickstart</groupId>
            <artifactId>graphql-java-tools</artifactId>
            <version>5.7.1</version>
        </dependency>
        <dependency>
            <groupId>com.graphql-java-kickstart</groupId>
            <artifactId>graphiql-spring-boot-starter</artifactId>
            <version>5.10.0</version>
        </dependency>

After the version update

 <dependency>
            <groupId>com.graphql-java-kickstart</groupId>
            <artifactId>graphql-spring-boot-starter</artifactId>
            <version>6.0.1</version>
        </dependency>
        <dependency>
            <groupId>com.graphql-java-kickstart</groupId>
            <artifactId>graphql-java-tools</artifactId>
            <version>6.0.0</version>
        </dependency>
        <dependency>
            <groupId>com.graphql-java-kickstart</groupId>
            <artifactId>graphiql-spring-boot-starter</artifactId>
            <version>6.0.1</version>
        </dependency>

What I have noticed after the update to 6.x.x:

• Package names have changed, so I had to modify each class implementing GraphQLMutationResolver , GraphQLResolver<T> or GraphQLQueryResolver
• The schema files do not get discovered anymore. Before the update the Queries and Mutation were available under the specified endpoint path. After the update my application only returns a 404 for the corresponding endpoint in combination with a GraphQL Post

The reason for the update is that I would like to implement the BatchLoder / DataLoader to prevent a query for each GraphQL property to resolve.

EDIT
What's also missing is the following log output when using the newer versions:
2020-03-02 08:04:37.857 WARN 16343 --- [ main] c.c.graphql.tools.SchemaClassScanner : Schema type was defined but can never be accessed, and can be safely deleted: SomeType

For me this means that the schemas are not discovered or scanned anymore.

[vojtapol]

You are posting this issue in the wrong project. The issue is already posted here: graphql-java-kickstart/graphql-spring-boot#353

Let's continue there.