Similar to before, maybe each history item doesn’t need to be its own model. If that’s the case, there are two ways to work with the data. You might think you could modify a history item like below and expect the UI to update, especially if you are coming from the Angular world:

model.get('history')[0].url='http://amazon.com';

However, this won’t work. If you need to modify a specific history item, you will need to use Ember.set. For example:

In the attrs property, set skills to { embedded: 'always' }. This also works for a belongsTo relationship. This example is using the JSONSerializer but the same technique can apply to an API based on the RESTSerializer. However, this does not work with the JSONAPISerializer at the time of this writing when I used Ember Data 2.3.3.

The EmbeddedRecordsMixin also works with nested data inside of nested data! For example, let’s say each skill now has an embedded category model: