Yes, i'd like to know that too. In my case it's especially frustrating to use resolve resources with authentication on routes. I don't want to redirect to other pages (e. g. error pages) after $routeChangeError event.
Am Freitag, 15. März 2013 11:07:33 UTC+1 schrieb [email protected]: > > Looking through the docs, and watching egghead.io videos, we get the > impression that resolve works as such: > > 1. nothing happens until all of the promises are resolved (changes are > deferred) > 2. if a resolve fails, nothing ever happens (other than the > $routeChangeError event) > > In fact, the is what is explicitly stated in the egghead.io videos. > > But... > 1. If you watch the egghead.io resolve tutorials carefully, you'll see > that something actually does happen (and immediately so) even when routes > do not get resolved. > 2. If you look through the source code for the 'Gmail-like routes' > tutorial, you'll find that there is actually only a single, re-used > controller > > Actually... > 1. some changes occur immediately, regardless of using promises/deferreds > a. although showing the new controller's content is deferred, the > previous controller's content is immediately removed (not gmail like) > b. the location is immediately updated > 2. even if a promise is rejected, there are side effects > a. the ng-view container is left empty (uh oh) > b. the window.history state remains polluted with the failed route path > > Am I misunderstanding the purpose of the resolve functionality? > > -- 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/groups/opt_out.
