Using generics with both SimpleObject and InputObject as field in output type fails

[kilork]

Hi, I encountered a weird issue I want to overcome somehow. Actually, I would be happy with w/a, because as alternative I have to generate quite massive structure with a lot of fields and I do not want to do this.

Expected Behavior

This code should work normally.

    #[tokio::test]
    pub async fn test_both_input_output_result_generic() {
        #[derive(SimpleObject, InputObject)]
        #[graphql(concrete(name = "MyObjectU32", params(u32)))]
        #[graphql(concrete(name = "MyObjectString", params(String)))]
        struct MyObject<T: InputType + OutputType> {
            a: T,
        }

        #[derive(SimpleObject)]
        struct MyObjectResult {
            fields: MyObject<u32>,
        }

        struct Query;

        #[Object]
        impl Query {
            async fn my_object_result(&self, fields: MyObject<u32>) -> MyObjectResult {
                MyObjectResult { fields }
            }
        }

        let _ = Schema::new(Query, EmptyMutation, EmptySubscription);
    }

• this test is based on https://github.com/async-graphql/async-graphql/blob/master/tests/input_object.rs#L411

Actual Behavior

It fails with the message:

Register `MyObjectU32` as `Object`, but it is already registered as `InputObject`

Steps to Reproduce the Problem

1. Have two structures, one generic with both SimpleObject and InputObject and second using first one, but only with SimpleObject annotation.
2. Use first structure as input parameter and second - as output in method declaration for some query.
3. Try to build a scheme with this query.

Specifications

• Version: 7.0.3
• Platform: n/a
• Subsystem: derive macros

[carlocorradini]

Any update?
I think the best solution is to allow
input_name in concrete:

 #[graphql(concrete(..., input_name="..."))]

This allows us to have both generic SimpleObject and InputObject with custom names avoiding conflicts