Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Getting errors after updating to Ember 2.8

See original GitHub issue

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.

Issue Analytics

State:
Created 7 years ago
Comments:17

Top GitHub Comments

3reactions

rwwagner90commented, Sep 27, 2016

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.

1reaction

rwwagner90commented, 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.