A decent component router was one of the MAIN things angular 1.X was lacking. The road to the new router has been and apparently still is full of bumps. It's a shame and making serious development very difficult for angular developers. This should be the team's priority number one. I feel very sorry about it being deprecated now. It just takes too long to get to a decent solution and drives developpers away from angular. You seriously underestimate the constant changes and it's implications for development. Swapping to a community solution , seriously? And facing a pile of refactorings when one wants to upgrade to angular2?
On Wednesday, June 15, 2016 at 3:49:59 PM UTC+2, Tim van der Heijden wrote: > > I just read that the component router in angular 1.5.7 is deprecated, > aaargh, I just refactored al my code to a component based strategy combined > with component router. Now I read that the component router is deprecated. > Anyone knows when it will be replaced and will the new router still be > component based? > > (see attachment) > > Cheers, > > Tim > -- 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.
