Explicitly register Java classes to the GraphQL schema. about graphql-spqr

[Balf]

@kaqqao I noticed your comments in #476 yesterday, both those aimed at nihila and myself, and took a look at the DefaultImplementationDiscoveryStrategy class. This actually already supports a method to add additional implemention classes, which resolves my issue quite nicely! My code now looks like this:

AnimalService animalService = new AnimalService();

GraphQLSchemaGenerator schemaGenerator = new GraphQLSchemaGenerator()
        .withBasePackages("io.leangen")
        .withOperationsFromSingleton(animalService)
        .withNestedResolverBuilders(new AnnotatedResolverBuilder());

var defaultImplementationDiscoveryStrategy = new DefaultImplementationDiscoveryStrategy();

//The new solution that just takes a class that implements IAnimal
for (var additionalImplementationProvider : additionalImplementationProvider) {
    // This line returns Llama.class from my original code
    Class<?> additionalImplementation = additionalImplementationProvider.getClass(); 
    defaultImplementationDiscoveryStrategy.withAdditionalImplementations(additionalImplementation);
}

schemaGenerator.withImplementationDiscoveryStrategy(defaultImplementationDiscoveryStrategy);

GraphQLSchema schema = schemaGenerator.generate();

This code takes the annotated Llama.class and adds it to the Schema as required, without having to define the entire type myself as per my previous solution. I'm closing this issue, as this solution does exactly what I wanted.

If you have time, could you take a look at #480 that I raised recently? That one is somewhat more complex and I don't know where to start in that case.

[kaqqao]

Yup, this looks good! 👍

Just 2 remarks:

• withBasePackages("io.leangen") - Not sure if it was just an example, but this should be your base package, so not io.leangen.
• withNestedResolverBuilders(new AnnotatedResolverBuilder()) - This is redundant. AnnotatedResolverBuilder is the default.

I'll have a look at #480.

[Balf]

Thanks for your feedback, the package name is indeed my own package in the actual code. The second point I'll update, cheers!

[Balf]

@kaqqao I'd like to contribute to the documentation, so I can add documentation for issues like mine. What would be the best way to do that?