I am working on a corporate Angular web application and am creating a proof of concept to add an "ease-out/ease-in" transition animation to all route changes. I've followed the Angular recommendations to a point, but I really don't want to add a data property to every single route in the entire app if I don't have to - there are over 500 routes across 50 modules. I tried simply returning "true" on getRouteAnimationData() but it only seems to work on the first page. Does Angular actually need this data property to handle the page transition, or might there be a way to get it to work without? Let me know if there's any other generic data I can provide - obviously with a corporate site, I can't post actual code, but it seems like it should work like any standard Angular web application. Continue reading...
