Artem Chivchalov

It is indeed very important subject for me also. Many cases assume that we need to solve several routes on the same map, for example, when trying to determine the...

@wingedfox Your provided example could be easily rewrited like this: ``` javascript $routeSegmentProvider .when('/section', 's1.idx') // you can use deep-level segment here .when('/section/index', 's1.idx') .segment('section', { template: '' }) .within()...

A bit unclear for me. You wrote: ``` javascript $routeSegmentProvider .when('/section', 's1') .when('/section/index', 's1.idx') .segment('section', { redirectTo: 'section/index' }) ``` This piece of configuration is identical to: ``` javascript $routeSegmentProvider...

OK, why not to use built-in angular `$routeProvider.when('/section', {redirectTo: '/section/index'})` for this case? I really see no reason for implementing redirects at segments level of abstraction.

I see. How do you assign segments to URLs in the case of these 5 routes?

Could you please create a test case reproducing this using jsFiddle, Plunker or something?

Hm, wouldn't we probably want to assign `otherwise` to a segment name, rather than to an URL?

@hupf Interesting scenario. I didn't think about the possibility to use `route-segment` module in conjunction with third-party view instead of `app-view-segment`, but it seems really feasible. > For this I...

@hupf Well, an important thing here is that wrapping `updateSegment(i, null)` into `$q.all()` is meaningless because of [this](https://github.com/artch/angular-route-segment/blob/master/src/route-segment.js#L254-L258). There are no resolving to be done, hence, it would be executed...

`routeSegmentChange` is single-segment event. You propose `routeSegmentChangeError` - OK, it's about single segment as well. But `routeSegmentChangesSuccess` is kinda overall finishing event, not related to any of them, so it...