We just spent a month moving an app to use the angular 1.5 component router so our next step to angular 2, when our platform supports it, would be easier.
Not good to find out the angular 1.5 component router has been deprecated and will not receive any updates!!! On Wednesday, June 15, 2016 at 11:25:37 AM UTC-6, Sander Elias wrote: > > 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.
