No custom enums as types in schema

I’d like to create and register a custom enum, for example:

enum AllowedColor {
    RED
    GREEN
    BLUE
}

and in my schema, to use it as a type:

color: {
    label: 'Color',
    type: AllowedColor,
    input: 'select',
    options: function() {
      // options for the select form control
      return [
        { value: 'RED', label: 'Red' },
        { value: 'GREEN', label: 'Green' },
        { value: 'BLUE', label: 'Blue' },
      ];
    }
  }

[eric-burel]

Hi,

We’ve discussed it with @Apollinaire and it actually seems to be a counter-productive idea, especially when taking values from allowedValues.

The biggest issue is that enums need to have a very specific format, the “Name” format in the GraphQL spec, which disallows most chars excepts letters, while allowedValues can be rich strings.

So the current solution to this issue specifying a custom GraphQL type for a field (not sure if we can do that yet? if not we will add this feature soon) + use the addGraphQLSchema function to define a new type.

We could support an additional field in the schema to directly specify enums but I am not sure the use case is worth it.

[eric-burel]

I confirm we will add the possibility to provide your own graphQL type in the future.

The current solution should be (not tested):

// trick: use a resolveAs to force a graphql field
myEnum: {
    type: String,
    resolveAs: {
         type: 'MyEnum'
    }
}
// add your enum type manually (we can't generate it for you)
addGraphQLSchema(`
    MyEnum Foobar Hello World
`)

In the future we will add a simpler way to specify a custom GraphQL type, we did not agree on an intuitive field name/syntax yet. I keep the issue open for reference but technically it is solved.