Allow custom directives

GraphQLSchema does not expose the use of custom directives. Based on the spec, the @skip and @include directives are required and appears to allow for custom directives.

The GraphQLSchemaConfig type doesn’t allow a list of directives, and neither does the GraphQLSchema allow directives through the constructor, but it is possible to set the _directives prop on the GraphQLSchema type, so it’s technically possible but not exposed.

[leebyron]

Closing this now as we’ve determined that user-supplied custom directives is a non-goal for graphql-js at this time.

[dschnare]

@leebyron Hmm. This doesn’t sit well with me. Directives are a great way for graphql server administrators to provide custom functionality to their graphql users.

From the spec:

GraphQL servers define what directives they support. For each usage of a directive, the directive must be available on that server.

This seems to be that so long as a directive can be found on the server the users of graphql should be fully capable of using said directive. Hence, there ought to be a way for graphql server administrators to add/register directives.

From my review of the source it appears that when instantiating a GraphQLSchema you can specify custom directives as part of the GraphQLSchemaConfig#directives config property, but there is no way to actually execute said directives (at least from what I can tell).

For those looking for similar functionality and not an outdated repo, try giving https://github.com/smooth-code/graphql-directive a look. Just don’t expect this to work forever.