createGraphQLHandler can't deal with directives about graphql

[jneurock]

Hi Tom, I'm so glad to hear the library works well for you... most of the time 😅

Could be that you need a custom resolver but I'd like to check how we can handle this from the library side, too.

I'll have to look into this issue more deeply. I might start with adding a test that includes a query with a directive. It's possible that this library just isn't friendly to directives. I'm pretty sure I didn't include any directives in the tests so they may be entirely unsupported 🙈

[thomasdittmar]

Hi @jneurock,

Thank you for looking into that.

Perhaps this piece of information will help you.

I already have custom resolvers setup. Something like that

getPerson(obj: any, args: any, context: any, info: any) {
  console.log(JSON.stringify(info.schema._directives))
  ... do more stuff here
  return mirageGraphQLFieldResolver(obj, args, context, info)
}

When I console log the schema directives I get the following result

["@include","@skip","@deprecated","@specifiedBy"]

Perhaps, that are the ones that are actually accepted and any custom one won't be recognised?

Cheers,

Tom

[jneurock]

Hey Tom,

I finally got time to look into this issue and it looks like you need to define the directive in your schema. See this section on Directives in the Apollo docs.

I added a fake directive to one of my queries and ran the tests. The tests failed with the exact error message you reported. Then I added a definition to the schema for my fake directive and the tests passed without issue.

Let me know if this helps and if it resolves this issue.

Thanks!

[jneurock]

Closing this issue for now but please feel free to reopen it, if need be. Thanks!