Directive disappears when an enum has resolvers defined

[kamilkisiela]

Using the following typeDefs with makeExecutableSchema should result in a GraphQLSchema that contains @auth directive but it fails when we define resolvers for an enum.

/**
 * directive that uses enum
 */
const typeDefs = `
  directive @auth(role: Role!) on FIELD | FIELD_DEFINITION

  enum Role {
    ADMIN
    USER
  }

  type Query {
    foo: String @auth(role: ADMIN)
  }
`;

Works

/**
 * Produced GraphQLSchema has @auth directive
 */
const schema = makeExecutableSchema({
  typeDefs,
});

console.log(schema.getDirective('auth')) // outputs: auth

Doesn't work

/**
 * Produced GraphQLSchema has no @auth directive, because enum has resolvers
 */
const schema = makeExecutableSchema({
  typeDefs,
  resolvers: {
    Role: {
      ADMIN: 'A',
      USER: 'U'
    }
  }
});

console.log(schema.getDirective('auth')) // outputs: undefined

Repro: https://stackblitz.com/edit/typescript-ktnvjs?file=index.ts

[yaacovCR]

Fixed in graphql-tools-fork, https://www.npmjs.com/package/graphql-tools-fork

[JForsaken]

Do we have an ETA on when the graphql-tools-fork fix for this will be merged into graphql-tools? 🙏

[yaacovCR]

Rolled into #1306