Flags enums are not correctly inferred.

Describe the bug If we infer a enum type form a flags enum like HotChocolate.Types.EnumType<System.Reflection.TypeAttributes we will run in to an error that the value names cannot be correctly inferred since each value can have multiple states leading to names like:

AUTOLAYOUT, ANSICLASS, CLASS, PUBLIC

To Reproduce

var schema = SchemaBuilder.New()
                .AddQueryType(c => c
                    .Name("Query")
                    .Field("foo")
                    .Type<StringType>()
                    .Resolver("bar"))
                .AddType<HotChocolate.Types.EnumType<System.Reflection.TypeAttributes>>()
                .Create();

Expected behavior This still has to be defined. Do we infer those as a list of enums. Leading to things like [[MyFlagsEnum]]?

Environment (please complete the following information):

• Version 10.0.1

[PascalSenn]

Plans yes, but it’s not a trivial change and there are a couple of other things before it in the backlog.

Essentially it would make sense to map the flag enum into a type:

[Flags]
public enum Foo { Bar=0,  Baz=1, Qux =2}

public class FooType : ObjectType<Foo> {
  protected override void Configure(IObjectTypeDescriptor<Foo> descriptor) 
  {
      descriptor.Field("isBar").Resolve(x => x.Parent<Foo>() & Foo.Bar == Foo.Bar);
      descriptor.Field("isBaz").Resolve(x => x.Parent<Foo>() &Foo.Baz == Foo.Baz);
      descriptor.Field("isQux").Resolve(x => x.Parent<Foo>() &Foo.Qux == Foo.Qux);
  }
} 

I guess as a workaround you could just define this type yourself

[jonmill]

Gotcha; so it sounds like the guidance right now is to add a converter to treat it (from the client perspective) as a numeric value, but the converter can convert it to the enum flags?

Is there a list of work to do for this? We use flags for a bunch of things in my company’s product, so I’d be interested in helping out 😃