Add override so serialiser saves hasMany

[backspace]

As suggested here by @fsmanuel.

What I missed in my previous pull request was that the dummy application wasn’t using the PouchDB serialiser!

[fsmanuel]

you don't need index:
import { Serializer } from 'ember-pouch';

[backspace]

Ah, thanks. I emulated this line. Changed now.

[fsmanuel]

The failing test is related to the change:

Integration | Adapter | Basic CRUD Ops: update an existing record

Error: Assertion Failed: A (subclass of DS.Model) record was pushed into the store with the value of ingredients being 'undefined', but ingredients is a hasMany relationship so the value must be an array. You should probably check your data payload or serializer.

I don't know if it's a bug in ember-data 1.13.

[backspace]

@fsmanuel, I was able to get the tests passing on Ember 1.13 by adding this override of serializeHasMany:

  serializeHasMany(snapshot, json, relationship) {
    this._super.apply(this, arguments);

    const key = relationship.key;

    if (!json[key]) {
      json[key] = [];
    }
  }

If the Ember Data implementation of serializeHasMany would result in an undefined attribute, this replaces it with an empty array. It seems kind of weird to me, but it works… do you think I should add this to the PR?

[fsmanuel]

@backspace LGTM!

[nolanlawson]

Seems to be failing only in Ember Data 1.13:

A (subclass of DS.Model) record was pushed into the store with the value of ingredients being 'undefined', but ingredients is a hasMany relationship so the value must be an array. You should probably check your data payload or serializer.

Do we want to drop support for 1.13 or is this fixable?

[backspace]

@nolanlawson: I just pushed that override for serializeHasMany that fixes it on 1.13. It’s a bit awkward but seems harmless.

[nolanlawson]

LGTM! Thanks for the fix; passing in Travis now.

[nolanlawson]

3cb2231