@model hash and did-update don't play well together about ember-render-modifiers HOT 3 OPEN

This sounds quite a bit like an issue that @wagenet was describing to me in an offline conversation. 🤔

from ember-render-modifiers.

@rwjblue I found this via another discussion; this is just a variant of the same issue you and I hit debugging internally a few weeks ago.

from ember-render-modifiers.

Nearly the same observations here, but with a 'single' model being returned from the model-hook.

Invoking a component like this in the route template:

<FooComponent @model={{@model}} />

Observing @model changes in the component template like this:

<div
  class="foo-component"
  {{did-update this.handleModelUpdate @model}}
  ...attributes
>
  FOO
</div>

Problem: the handleModelUpdate action gets triggered when switching sub-routes although its own route is unchanged and the model hook never fired. Changing the model param value from @model to this.model fixes it:

<FooComponent @model={{this.model}} />

from ember-render-modifiers.