hasMany relationship was broken

[amarpalsapure]

During serializing object, object with hasMany were not getting serialized. Small fix is required. Hope this helps.

[bradleypriest]

@amarpalsapure could you please add a test

[amarpalsapure]

I tried to do that, but not sure how to do that in json_serializer.js. I will need to create some temp objects but not sure how to create them. Currently in my project the solution is working. I have posted an answer on stackoverflow also http://stackoverflow.com/a/18739320/1113246

[bradleypriest]

Hmm, the bug they were running into was actually fixed here be954be

[wycats]

This definitely needs to be thought through more fully, but the current default serialization strategy is to serialize one-to-many relationships on the belongsTo side.

It doesn't really make sense to serialize it on both sides, but I can see where you might want to serialize it on the many side (for document oriented databases).

You can easily get the behavior you want in your app by overriding the small serializeHasMany method in your own ApplicationSerializer to something like this:

App.ApplicationSerializer = DS.Serializer.extend({
  serializeHasMany: function(record, json, relationship) {
    var key = relationship.key;

    // don't care which kind of hasMany relationship this is
    json[key] = get(record, key).mapBy('id');
  }
});

@bradleypriest maybe we should make this the default behavior and make the "serializes on the belongsTo side" behavior of the AMSerializer? What do you think?

[amarpalsapure]

@bradleypriest I have taken the latest canary build, but the problem still persist.

Thanks @wycats, I did as you suggested and it did work, small change I did was instead of doing get(record, key) I need to do Ember.get(record, key).

[wycats]

In your own app you can just do record.get(key). In Ember itself the coding style is to always use the functional form.

[amarpalsapure]

Thanks @wycats for the info and it did work.

[bradleypriest]

@wycats I'm incredibly Rails-biased myself, I've never actually worked with an API that serializes the hasMany.