Artem Chivchalov
Artem Chivchalov
Yes, `$routeSegment.$routeParams` is populated only when the segment is switched, it is the very meaning of it -- to preserve the state of `$routeParams` of the _currently active_ segment, not...
What is `params`? There are no such option in segment's config.
This variable has nothing to do with segment's configuration object. It is for internal use and is not accessible from external consumers.
Could you please make a plunker illustrating this issue?
The prefix is managed by $location service itself, it is not $routeSegment's responsibility. Moreover, links can be rewritten by the application or Angular itself, using its own knowledge about application...
`routeSegmentUrl` filter is just a wrapper around `$routeSegment.getSegmentUrl()`. If it was returning an URL with a hash, then this would not work: ``` javascript $location.path($routeSegment.getSegmentUrl('one')); ``` You have to either...
Did you have a look to `watcher` property? ``` javascript .segment('index', { ... watcher: function(injectables) { ... return result; // when result is changed, the segments gets reloaded } })...
Please describe this a bit more. What use scenario is broken otherwise? Could you please write a unit test for this case?
Do we have an example of how to use such pipelines?