Hi Tim, Well, the component router was actually the back-ported router off Angular 2. However, during testing a few things surfaced that where next to impossible to fix. Also, lazy loading was apparently not possible. At least not well. So the hard decision was made, and yet another replace came to life. Once it's stable enough (and proven that it will do anything that's needed) the work of back-porting it to NG1 will start again.
For your accordion. I'm not sure that can be solved with a router. For myself, I would build a component that reacts to the current route, but isn't actual a view-port. Regards Sander -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
