No matter the validation error, I still get generic Argument Validation Error message

[geauser]

Describe the Bug
When there is an error caught by class-validator decorators on @InputType() for mutations (example @MinLength), I only get a generic "Argument Validation Error" message.

Furthermore specifying a custom validation message as documented in class-validator doesn't change anything.

To Reproduce
I made a dedicated repo to reproduce the problem.

When the server is up, executes this query on http://localhost:4444/gql:

mutation { 
    addAccount(data: { name: "Invalid" }) { name }
}

Expected Behavior
I'd expect to see the validation message set for the given class-validator decorator (or the default one).

Logs

{
    "errors": [
        {
            "message": "Argument Validation Error",
            "locations": [
                {
                    "line": 2,
                    "column": 5
                }
            ],
            "path": [
                "addAccount"
            ]
        }
    ],
    "data": null
}

Environment

• OS: MacOS 12.4 Monterey
• Node v16.13.2
• Package version ^2.0.0-beta.1
• TypeScript version ^4.9.4

[MichalLytek]

Is it a duplicate of #1396 ?

[geauser]

Hmm does not seem like it. Passing { forbidUnknownValues: false } changes nothing.

[carlocorradini]

Duplicate of #1397
The GraphQL error encapsulates the original error.
You must create a custom function (formatError) when building an Apollo server instance.
It's all described in this comment: #1397 (comment)