Support for Server Errors

I believe support for error messages was accidentally dropped in 2.0.0-beta.9 is missing.

Error (origin):

ERROR Error: invalid parameters
    at updateResourceErrorsForQuery (ngrx-json-api.es5.js:606)
    at NgrxJsonApiStoreReducer (ngrx-json-api.es5.js:2520)
    at combination (store.es5.js:46)
    at combination (store.es5.js:46)
    at ScanSubscriber.reduceState [as accumulator] (store.es5.js:346)
    at ScanSubscriber.webpackJsonp.../../../../rxjs/operator/scan.js.ScanSubscriber._tryNext (scan.js:109)
    at ScanSubscriber.webpackJsonp.../../../../rxjs/operator/scan.js.ScanSubscriber._next (scan.js:102)
    at ScanSubscriber.webpackJsonp.../../../../rxjs/Subscriber.js.Subscriber.next (Subscriber.js:89)
    at WithLatestFromSubscriber.webpackJsonp.../../../../rxjs/operator/withLatestFrom.js.WithLatestFromSubscriber._next (withLatestFrom.js:113)
    at WithLatestFromSubscriber.webpackJsonp.../../../../rxjs/Subscriber.js.Subscriber.next (Subscriber.js:89)

Server Response (reference) with 422:

{
  "errors": [
    {
      "detail": "field may not be empty",
      "source": {
        "pointer": "/data/attributes/x"
      },
      "status":"422"
    }
  ]
}

[remmeier]

yes, that invalid parameters check is now too strict. Previously it did not recognize invalid calls to that method. A bit of type-safety in that area would not hurt.