Multiply level inheritance chain is broken. about iron-router HOT 3 CLOSED

Yeah I guess my approach was naive, since I'm not controlling which order the prototype chains actually get hooked up in. So, it looks like this happens when the SuperController also uses create but it's prototype chain gets connected after the child prototyping has already completed. Sigh. Investigating.

from iron-router.

Okay, I think I'm going to call this inheritance order thing a botch for now. See #10. My solution only caused inheritance to be delayed until after initial script loading, but didn't build a dependency tree so it only works in some cases. I think that @tmeasday is right - this belongs in Meteor. So for now I'll convert my controllers into a package to control load order in our app and roll back the changes I made to the router.

from iron-router.

Keeping list of things to lobby Meteor for pre 1.0. After the fiasco of moving controllers into a package, I'd have to say, controlling load order in app space is a high priority for us at least :-).

from iron-router.