Graphql-js: Enum value is not resolved to internal value for directive argumets and default values

Created on 12 Dec 2018 · 7Comments · Source: graphql/graphql-js

the original issue was submitted to the graphql-tools repo, but it seems that it never made it here.

the issue is that after following the official documentation the enum value is not resolved to the internal value when used as a default value or in directives.

the test attached to the original issue provided by @JakeDawkins
https://gist.github.com/JakeDawkins/66f5b026cf21515f1004f057754a2cd4

question

Source

raduflp

❤1

All 7 comments

@raduflp With current graphql-js design defaultValue should be in internal representation. So to correct @JakeDawkins example you need to do:

const schema = new GraphQLSchema({
  query: new GraphQLObjectType({
    name: 'Query',
    fields: () => ({
      avatar: {
        type: GraphQLBoolean,
        args: {
          anEnum: {
            type: allowedColor,
            defaultValue: '#f00',
            //            ^ Changed to value
          },
        },
        resolve: (root, args) => (args.anEnum === '#f00' ? false : true),
      },
    }),
  }),
});

Same goes for custom scalars, arrays or any other example of input coercion.
For example ID coerce numbers to strings but this coercion is not applied on defaultValue:

const schema = new GraphQLSchema({
  query: new GraphQLObjectType({
    name: 'Query',
    fields: () => ({
      avatar: {
        type: GraphQLBoolean,
        args: {
          id: {
            type: GraphQLID,
            // INVALID defaultValue: 0
            defaultValue: '0', //VALID
          },
        },
      },
    }),
  }),
});