You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using Ember canary, when an "outer" component has an "inner" component that's inside a wormhole, and the "inner" component sends an action, the action is fired on the wormhole itself, causing the error:
Uncaught Error: <emberapp@component:ember-wormhole::ember609> had no action handler for: actionName
It used to be fired correctly on the "outer" component, but is broken since emberjs/ember.js#12289.
I've also raised an issue on the ember.js repository: emberjs/ember.js#12317, but thought the issue may be able to fixed on the ember-wormhole side, or you might have some insight into how to fix the regression.
Note that this is only an error if the "inner" component and wormhole are defined in an "outer" component template; the action works fine if the component/wormhole are in a controller template.
Using Ember canary, when an "outer" component has an "inner" component that's inside a wormhole, and the "inner" component sends an action, the action is fired on the wormhole itself, causing the error:
It used to be fired correctly on the "outer" component, but is broken since emberjs/ember.js#12289.
I've also raised an issue on the ember.js repository: emberjs/ember.js#12317, but thought the issue may be able to fixed on the ember-wormhole side, or you might have some insight into how to fix the regression.
Note that this is only an error if the "inner" component and wormhole are defined in an "outer" component template; the action works fine if the component/wormhole are in a controller template.
This fiddle reproduces the issue: http://ember-twiddle.com/1c59a1dcdb18eec69a8e. Changing the ember dependency from
canary
torelease
intwiddle.json
fixes the issue.The text was updated successfully, but these errors were encountered: