refactor: change error message format to multiline

[callmehiphop]

Fixes googleapis/nodejs-bigquery#326

• Tests and linter pass
• Code coverage does not decrease (if any source code was changed)
• Appropriate docs were updated (if necessary)

---

Using the following server error for the before/after

{
  "state": "DONE",
  "errorResult": {
    "reason": "invalid",
    "location": "",
    "message": "Error while reading data, error message: JSON table encountered too many errors, giving up. Rows: 1; errors: 1. Please look into the errors[] collection for more details."
  },
  "errors": [
    {
      "reason": "invalid",
      "location": "",
      "message": "Error while reading data, error message: JSON table encountered too many errors, giving up. Rows: 1; errors: 1. Please look into the errors[] collection for more details."
    },
    {
      "reason": "invalid",
      "location": "",
      "message": "Error while reading data, error message: JSON parsing error in row starting at position 0: Could not convert value to string. Field: caller; Value: 822"
    }
  ]
}

Before

Error while reading data, error message: JSON table encountered too many errors, giving up. Rows: 1; errors: 1. Please look into the errors[] collection for more details.
    at endReadableNT (_stream_readable.js:1081:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)

After

Multiple errors occurred during the request. Please see the `errors` array for complete details.

    1. Error while reading data, error message: JSON table encountered too many errors, giving up. Rows: 1; errors: 1. Please look into the errors[] collection for more details.
    2. Error while reading data, error message: JSON parsing error in row starting at position 0: Could not convert value to string. Field: caller; Value: 822

    at endReadableNT (_stream_readable.js:1081:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)

[JustinBeckwith]

Is there any way this could be breaking?

[callmehiphop]

@JustinBeckwith I think if users did any kinds of string/regexp operations against the error message, it would definitely throw them for a loop. If preferable, I could just make some new custom errors in the BigQuery lib itself, but it would still be a breaking change in the same capacity, which would require a semver major bump.

[stephenplusplus]

Can you do a before / after?

[callmehiphop]

@stephenplusplus if you go to the linked issue, there's a pretty good diff on the two.

[stephenplusplus]

I didn't see it. Could you do one for here anyway in the opening post so it's easier for users and future us? :)

[callmehiphop]

@stephenplusplus I just updated the overview with some examples. PTAL!

[stephenplusplus]

This does make it easier to read, but since we're here, we could probably kick it up a notch:

Multiple errors occurred during the request. Please see the `errors` array for complete details.

    1. Error while reading data, error message: JSON table encountered too many errors, giving up. Rows: 1; errors: 1. Please look into the errors[] collection for more details.
    2. Error while reading data, error message: JSON parsing error in row starting at position 0: Could not convert value to string. Field: caller; Value: 822

    at endReadableNT (_stream_readable.js:1081:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)

[callmehiphop]

@stephenplusplus SGTM - PTAL :)

[stephenplusplus]

@callmehiphop would you mind updating the first post with the new formatting?

[callmehiphop]

@stephenplusplus sure, done!

[oliverwoodings]

Thanks so much for getting this done! Love how quickly you guys pick up and resolve issues. 🎉