How to add a Directive?

[crumhorn]

In the documentation for graphql-java, they use RuntimeWiring to create a directive as:

wiring.directive("directiveName", new SchemaDirectiveWiringImpl())

The only way I see how to add a directive here is to create the GraphQlSchema object and then do a:

GraphQLSchema newSchema = GraphQLSchema.newSchema(justCreatedSchema).additionalDirective(new SchemaDirectiveWiringImpl()).build();

However, in that code, they don't take a SchemaDirectiveWiring interface as an argument, but a GraphQLDirective class, which seems to have zero possibility to actually convert an object from A to B as the data passed to it and methods available are just lacking. Also, if I go that route, my overridden methods don't actually get called anyway, no matter what I set.

So, is there a way to add a directive somehow or am I out of luck? I don't mind merging graphql-tools and graphql-java in some way when creating the schema but I can't seem to find a way to get my directive in there using graphql-java-tools (and I really don't want to use the normal way of declaring every data fetcher etc)

[CH-EricLundberg]

I would love to know how to get access to the underlaying graphql-java schema after it has been autowired by graphql-java-tools. Then I could tweak some stuff by hand that doesn't autowire well. Is there some kind of post construction hook?

[gipeshka]

As of what I've seen in the code I have a small question related to directives.
In schema parser when creating an input object the field doesn't get the directives added, even though the definition contains all the required data. Why is that so?

@CH-EricLundberg I guess you can inject GraphQLSchema, it's wired via GraphQLJavaToolsAutoConfiguration

[oliemansm]

@crumhorn Not familiar with wiring and directives myself. Although those directives seem pretty useful at first glance. Looking at graphql-java-tools it creates the schema programmatically in SchemaObjects like this:

fun toSchema(): GraphQLSchema = GraphQLSchema.newSchema()
        .query(query)
        .mutation(mutation)
        .subscription(subscription)
        .build(dictionary)

This is the last step after parsing the SDL and it has created the necessary GraphQLObjectType objects.

When I look at the documentation of graphql-java, especially about wiring, it seems to use an entirely different approach for creating the schema.

So either graphql-java would have to add support for the type of directives you need, or graphql-java-tools would have to use a different approach in creating the schema. I think that is some serious amount of work though.

[enriquedacostacambio]

maybe i'm missing something, but i think it would be great to have the option of using graphql-java-tools only as a graphql.schema.idl.WiringFactory that can then be combined with other wiring factories.
for example: to combine typed resolvers with generic fetchers, or to add directive wirings.

[oliemansm]

This will be available in 5.4. See https://www.graphql-java-kickstart.com/tools/directives/ for more details.

[alexgenco]

Any plans to add support for ENUM_VALUE? Our use case is to determine whether to convert enum values to all upcase depending on the version of the client making the request (for backwards compatibility).

[oliemansm]

Yeah, will take a look at it.

[oliemansm]

@alexgenco Will be available in 5.4.1.

[alexgenco]

@oliemansm thanks for doing this. Is there a way to override the datafetcher for an enum value at query execution time, like the documentation examples do for FIELD_DEFINITION directives? I'd like to use DataFetcherFactories.wrapDataFetcher, but the GraphQLEnumValueDefinition object doesn't expose it.

[oliemansm]

@alexgenco That's actually functionality from graphql-java. Could you raise an issue over there how you should be handling this? Either on their github or through their Spectrum channel. I'm not sure what hook is available during query execution time for this type. And you probably don't want to have to add a directive to every location where you use the enum to handle it using the FIELD_DEFINITION.