Gavin Joyce
Gavin Joyce
Great, thanks. I'll work on this soon.
A workaround is to add a debounce to the `onChange` in the consuming app
Hey @BryanCrotaz. I still use this addon in production, it's working great for me. I don't really need more from the addon at the moment, so I haven't been that...
Does https://headlessui.com/ have one of those? If not, I think it probably doesn't belong in this addon.
I'm not sure why this is failing on CI: It passes locally:
@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...
@Maarius @jamesdixon I've created a [spike](https://github.com/GavinJoyce/ember-component-inbound-actions/pull/23) which seems to work pretty well: The name form uses the new mechanism, the address form uses the old
@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.
It sounds like you could use contextual components and closure actions. Is there any reason why you couldn't? I'm interested as I suspect that this addon might not have any...
That is confusing. The intention is for `scheduleInAfterRender` to run on any version of ember newer than 1.12