For the love of the gods, and science, and empirical rationalism only being able to setup static $routes in a module's .config is extremely limiting, lacking the great magic of services, and other goodies.
Why is this so? What if I want to inject headers, or parameters into the templateUrl based on later user authentication, do I just have to reload the page after user auth? What if I want to retrieve a controller from the server based on session token instead of dumping everything onto the client at runtime w/out any idea of user authentication? Should I avoid #hash routes for such things? i love you angular, i hate you, i love you. -- 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 angular+unsubscr...@googlegroups.com. To post to this group, send email to angular@googlegroups.com. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/groups/opt_out.
