Error responses for mutations with arrays in input is confusing, how to interpret?

[Bertg]

I have the following mutation (cleaned up):

{
    "query": "mutation ImportMembers($input: MembersImportMutationInput!) { importMembers(input: $input) { result } }",
    "variables": {
        "input": {
            "importLines": [
                {
                    "name": "Foo Bar",
                    "email": "[email protected]",
                    "externalId": "123",
                    "details": [
                        {
                            "fieldId": "123445",
                            "phoneNumberValue": {
                                "value": "12345_67890"
                            }
                        }
                    ]
                }
            ]
        }
    }
}

In this mutation the phoneNumberValue.value 12345_67890 will fail validation on that type:

class PhoneNumberValueInputType < GraphQL::Schema::InputObject
  graphql_name "PhoneNumberValueInput"
  description "Input values for a phone number input"
  argument :value, String, required: true, prepare: ->(phone_number_value, _ctx) {
    phone_number_value.gsub(/\p{Space}+/, " ")
  }, validates: { format: { with: /\A[\p{Space}]*\+?[0-9#\*\.\(\)\-\p{Space}]+\Z/u } }
end

And this is the error we get back:

{
    "errors": [
        {
            "message": "value is invalid",
            "locations": [
                {
                    "line": 4,
                    "column": 3
                }
            ],
            "path": [
                "importMembers"
            ]
        }
    ],
    "data": {
        "importMembers": null
    }
}

So I have a few questions:

• What are lines and columns actually referring the here?
• How would I be able to get an error that actually points to the exact path of the item that failed validation? In this case something like: input.importLines.0.details.0.phoneNumberValue.value

[rmosolgo]

line and column refer to a location in the original query string. I see the query string in your example has no newlines in it ... but was that because of how you "cleaned it up" to post here?

There isn't much for "input path" tracking in GraphQL-Ruby right now, though it was discussed in #5266

[Bertg]

Yeah, it is cleaned up, so that will be it.

But here there is nothing wrong with the query itself.
An input validation failed, so the current error is not very useful, somewhat misleading even.

Is there a way we could add this ourselves? Or is this something the library would need to support?