Connection Builder seem to only support a single type

[seekdavidlee]

Hi, I have a project that attempts to build a generic Type around a model which contains attributes necessary for building out the fields. This way, developers would only be focused on the model. For the example below where Droid is the model:

Connection<DroidType>() .Name("friends")

It would be translated internally to the following. The "Type" is built-in via ModelConventionType.

Connection<ModelConventionType<<Droid>>() .Name("friends")

I was able to use this technique in version 2.x to create multiple Connections for different paging requirements. Maybe one would be require a argument and the other does not.

Connection<ModelConventionType<<Droid>>() .Name("friends") .Argument<NameType>("name", "Name of friend")

It seems this no longer works in 3.x. I am getting the following error: the name 'ModelConventionConnection' is already registered to 'GraphQL.Types.Relay

As an experiment, if I create ModelConventionType2 but with the same type of Droid being reused in additional to a connection with ModelConventionType, it is also complaining of a similar error.

[rheid]

The issue from @seekdavidlee It’s also really important for my project. I hope you can offer a solution in the framework.

[Shane32]

Could this be due to a failure of the automatic naming of types within GraphQL.NET to handle generic types?