Using actionReceiver attribute for component causes the component to immediately rerender after being rendered about ember-component-inbound-actions HOT 6 OPEN

@Maarius thanks for reporting this. It's likely that as we're calling this.set('actionReceiver', proxy); in an afterRender, a rerender is happening.

I've come across similar behaviour when trying our app out with Glimmer and we've been experimenting with alternative mechanisms of sending inbound actions to components that avoid the this.set in the afterRender. I'll post more here when we've completed our experiments.

from ember-component-inbound-actions.

@GavinJoyce any update on this? Cheers.

from ember-component-inbound-actions.

@Maarius @jamesdixon I've created a spike which seems to work pretty well:

The name form uses the new mechanism, the address form uses the old

from ember-component-inbound-actions.

Any news on that? I came across the issue by accident with 2.1.2 when I observed my didReceiveAttrs hook being triggered twice even though no attributes had been changed in the business logic. Checked the linked spike but it seems like there's no final conclusion yet?

from ember-component-inbound-actions.

@digitalbreed I haven't made any further progress spike, mainly as I think the use of ember-component-inbound-actions is an anti-pattern in Ember 2.0+. Contextual components are a much better solution.

from ember-component-inbound-actions.

Agreeing with @GavinJoyce on the anti-pattern side of things but having to support existing code and 'control' third party components (+ experiencing re-renders with ember-component-inbound-actions) led me to create https://github.com/andyhot/ember-cli-puppet

Usage is almost the same as ember-component-inbound-actions though you do get more power as to who receives the component instance - @digitalbreed take a look and ping me if that doesn't solve your problems

from ember-component-inbound-actions.