Sander, When you said you haven't seen a user case that could not be solved by the new router, are you referring to the yet to be published features, or the already published features?
I have a use case that I don't know what template to use until run time. When I get the value A back from the server, I want to use template A; and when I get B back, I want to use template B. Right now, I am using ng-include. But how can I solve this with the new router? Also, one other thing, I want to include different CSS for different components; right now, I am embedding the css with the [component].html, how can I specify different css in the router? Thanks, Derek On Friday, May 1, 2015 at 12:25:47 AM UTC-7, Sander Elias wrote: > > Hi Derek, > > I haven't seen a use case that could not be solved by the new router. Some > of them need some rethinking tough. > > 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 http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
