Custom error fields are not proxied

In order to handle forms validation I’m going to use additional fields inside regular errors (to mention exact fields and failed validation rules), however looks like additional field are not proxied at all.

For example: original endpoint gives me response:

{
  "errors": [
    {
      "message": "An unknown error occurred.",
      "category": "auth",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "authUser"
      ]
    }
  ],
  "data": {
    "authUser": null
  }
}

e.g. with custom field category, and while proxying same query via faker - just

{
  "data": {
    "authUser": null
  },
  "errors": [
    {
      "message": "An unknown error occurred.",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "authUser"
      ]
    }
  ]
}

So my custom category field is lost.

What do you think about proxying complete error?

[RomanHotsiy]

oops 🙈 , try v1.6.2 plz

[IvanGoncharov]

@caseycs Should be pretty easy to fix, I will try to fix it this weekend.