Resolves behave differently from ngRoute

[d6u]

Example: http://plnkr.co/edit/5tqVwC

Question 1:

The example showed how redirection in resolve function will affect template and controller. When using route-segment, redirection in before resolve resolved is temporary. Once the resolve finish, original controller and template (OneCtrl and template-one) will be loaded back into <div app-view-segment></div> and keeping url with #/three.

On the other hand, ngRoute will not load OneCtrl and its template back into ng-view after redirection.

Question 2:

The example did not illustrate this problem.

But if I'm using a service name as resolve, the service function will be executed every time I route to that address. Not like in ngRoute, only function resolver will be executed every time, service resolver will only be executed once, which is the right behavior of a service.

Question 3:

Will this module support the new controllerAs syntax?

---

I really love this nested view module, especially the untilResolve option. Thank you in advance.

[artch]

1. Yes, this is known issue. I'm working on it.
2. Could you please provide a sample for it? Resolving uses $injector.get method which should operate properly regarding singleton caching, etc.
3. You might use such syntax, it works:

.segment('s1', {
    templateUrl: 'template',
    controller: 'MyCtrl as myCtrl'
})

[d6u]

Please ignore question 2, it's working now, I must got something wrong.