Not informative INTERNAL_SERVER_ERROR when mutation has invalid input as variable

[ph55]

If mutation request made with input variable and it has invalid data - error not informative.
Example:

• Good. Login mutation with regular input

mutation {
  login(input: {
    username: "user",
    password: 1
  })
}

Response:

{
  "errors": [
    {
      "message": "Expected type String!, found 1.",
      "locations": [
        {
          "line": 4,
          "column": 13
        }
      ],
      "extensions": {
        "code": "GRAPHQL_VALIDATION_FAILED"
      }
    }
  ]
}

---

• Bad. Login mutation with variable input

mutation login($input: LoginInput!) {
  login(input: $input)
}

variables:

{
  "input": {
    "username": "user",
    "password": 1
   }
}

Response:

{
  "errors": [
    {
      "message": "Internal server error",
      "locations": [
        {
          "line": 1,
          "column": 16
        }
      ],
      "extensions": {
        "code": "INTERNAL_SERVER_ERROR"
      }
    }
  ]
}

As you can see there is zero information regarding error. Also it should be GRAPHQL_VALIDATION_FAILED instead of INTERNAL_SERVER_ERROR.
Only if with debug on you can see the error:

{
  "errors": [
    {
      "message": "Internal server error",
      "locations": [
        {
          "line": 1,
          "column": 16
        }
      ],
      "extensions": {
        "code": "INTERNAL_SERVER_ERROR",
        "exception": {
          "stacktrace": [
            "TypeError: String cannot represent a non string value: 0",
            "........."
          ]
        }
      }
    }
  ]
}

Probably related to #1410
Still opening this one since it have a bit more information.

This is a big issue since normal API couldn't be built without error info.

[kfrajtak]

I am afraid this does not work in 2.6.7.

[glasser]

Duplicate of #3498

[glasser]

I've released a prerelease with this fix, version 2.23.0-alpha.0. Try out the alpha and see if it works for you! Please provide any feedback in #5094.

[glasser]

(as a workaround you can also switch your setup to using payloadFormatVersion 1.0)

[glasser]

This is released in Apollo Server 2.23.0.