Async-graphql: Invalid error messages for scalar arrays

[hapcode]

Expected Behavior

Output 1 for fewReq: [DateTime!]! (should have trailing exclamation):

{
    "message": "Failed to parse \"DateTime\": trailing input (occurred while parsing \"[DateTime!]!\") (occurred while parsing \"TestInput\")",
}

Output 2 for fewOpt: [DateTime!] (should have no duplicates):

{
    "message": "Failed to parse \"DateTime\": trailing input (occurred while parsing \"[DateTime!]\") (occurred while parsing \"TestInput\")",
}

Actual Behavior

Output 1 for fewReq: [DateTime!]! (missing trailing exclamation):

{
    "message": "Failed to parse \"DateTime\": trailing input (occurred while parsing \"[DateTime!]\") (occurred while parsing \"TestInput\")",
}

Output 2 for fewOpt: [DateTime!] (duplicates):

{
    "message": "Failed to parse \"DateTime\": trailing input (occurred while parsing \"[DateTime!]\") (occurred while parsing \"[DateTime!]\") (occurred while parsing \"TestInput\")",
}

Steps to Reproduce the Problem

SDL and code:

input TestInput {
    fewReq: [DateTime!]!
    fewOpt: [DateTime!]
}

```rust

[derive(InputObject)]

pub struct TestInput {
few_req: Vec>,
few_opt: Option>>,
}

Query:
```gql
mutation Test($input: TestInput!) {
  test(input: $input)
}

Input 1:

{ 
  "input": { 
    "fewReq": ["2020-01-01T00:00:00+00:00err"],
    "fewOpt": ["2020-01-01T00:00:00+00:00"]
  } 
}

Input 2:

{ 
  "input": { 
    "fewReq": ["2020-01-01T00:00:00+00:00"],
    "fewOpt": ["2020-01-01T00:00:00+00:00err"]
  } 
}

Specifications

• Version: 2.0.12
• Platform: MacOS

[sunli829]

@Koxiaet When you have a moment, would you please help me look at this problem? 🙂

[Kestrer]

Should be fixed now with 9d94c93.

[hapcode]

Should be fixed now with 9d94c93.

I don't want to sound boring but this fix is for the Output 2. In async-graphql 2.1.1 I have identical errors for both types [DateTime!]! (<-- trailing exclamation) and [DateTime!]. I don't think it's important, just my note.