ember-route-action-helper: Getting errors after updating to Ember 2.8

TypeError: Cannot read property 'currentHandlerInfos' of undefined
    at getRoutes (http://localhost:7357/assets/vendor.js:200596:36)
    at getRouteWithAction (http://localhost:7357/assets/vendor.js:200601:30)
    at Class.compute (http://localhost:7357/assets/vendor.js:200626:33)
    at Object.compute (http://localhost:7357/assets/vendor.js:31074:26)
    at Object.value (http://localhost:7357/assets/vendor.js:31404:27)
    at Object.read (http://localhost:7357/assets/vendor.js:31797:21)
    at Object.getCellOrValue [as default] (http://localhost:7357/assets/vendor.js:26779:39)
    at snapshotAndUpdateTarget (http://localhost:7357/assets/vendor.js:30179:60)
    at createComponent (http://localhost:7357/assets/vendor.js:30138:5)
    at Function.ComponentNodeManager_create [as create] (http://localhost:7357/assets/vendor.js:30027:17)

Not sure exactly what the cause may be.

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 17

Commits related to this issue

Reference passed action instead of `route-action` This will work the other way, but will cause test failures in components that do that. See https://github.com/DockYard/ember-route-action-helper/issu... — committed to travis-ci/travis-web by deleted user 7 years ago
Reference passed action instead of `route-action` This will work the other way, but will cause test failures in components that do that. See https://github.com/DockYard/ember-route-action-helper/issu... — committed to travis-ci/travis-web by deleted user 7 years ago
Reference passed action instead of `route-action` This will work the other way, but will cause test failures in components that do that. See https://github.com/DockYard/ember-route-action-helper/issu... — committed to travis-ci/travis-web by deleted user 7 years ago

Most upvoted comments

I would love to see an option to enable this again or something. With a warning that it goes against the traditional DDAU principles somewhat.

RobbieTheWagner on Sep 27, 2016

@ilucin the components are not specific to routes in our use cases. Think of components used across many routes and you have an action on all their parent routes myComponentChanged. You could fire this directly and have each route do different things, still with a generic component, not specific to the route.

RobbieTheWagner on Sep 27, 2016

For those with this issue, I recommend reverting to version 1.0.0. I bumped #37 to 2.0.0 since I considered it a breaking change.

poteto on Sep 27, 2016

This issue was introduced for me in the upgrade to ember-route-action-helper on ember 2.4 LTS. It happens in integration tests where the router is not present.

@martndemus Here is a twiddle that repros the problem.

blimmer on Sep 27, 2016