# Child component does not re-render on model change

**URL:** <https://discuss.emberjs.com/t/child-component-does-not-re-render-on-model-change/8249>\
**Category:** Uncategorized\
**Created:** [June 22, 2015, 5:31pm UTC](https://discuss.emberjs.com/t/child-component-does-not-re-render-on-model-change/8249 "2015-06-22T17:31:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ohnnyj](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/ohnnyj/32/10924_2.png) [@ohnnyj](https://discuss.emberjs.com/u/ohnnyj)\
**Post date:** [June 22, 2015, 5:31pm UTC](https://discuss.emberjs.com/t/child-component-does-not-re-render-on-model-change/8249/1 "2015-06-22T17:31:21Z")

</div>

Maybe I am doing this wrong here but here it goes.

I have a component which iterates over an array of ember objects using #each, creating a child component for each entry. This array is the component’s model. Each item in the array is the model for each child.

Later when I call set(‘model’, model); on a child component it does not refresh. When I set individual properties on the model it does refresh.

The parent template:

{{#each model as |m|}} \<item-view model={{m}} \> {{/each}}

The child template:

\<img src={{model.image}} /\> {{model.title}}

I am using the latest canary build of Ember ([Merge pull request #11511 from stefanpenner/deprecate-ember-create-keys · emberjs/ember.js@af98f59 · GitHub](https://github.com/emberjs/ember.js/commit/af98f598ee1d1ec063854f575c3fa58cce099c23)).

---

<div class="post-metadata">

**Author:** ![neojp](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/neojp/32/15934_2.png) [@neojp](https://discuss.emberjs.com/u/neojp)\
**Post date:** [June 23, 2015, 1:23am UTC](https://discuss.emberjs.com/t/child-component-does-not-re-render-on-model-change/8249/2 "2015-06-23T01:23:23Z")

</div>

I might have missed something when I read your message, but when using `bracket components` you can’t change the paren’t model object unless you use `mut`.

> **[The Transition to Ember 2.0 in Detail](https://blog.emberjs.com/run-up-to-two-oh/)**
>
> As we approach the eve of the release of Ember 1.13-beta, it's a good time to talk about the transition plan for those of us who have Ember 1.11...

Maybe this is your issue? If not, maybe replicating this in a [jsbin](http://emberjs.jsbin.com/) might help others understand your problem.