Same segment, different parameters == no segment update.

[airtonix]

Similar to this issue: #15

Except that here is the condition:

Same url pattern thus same segement, but different parameters.

Since this is the logic that determines whether or not to update the segment, we also need to test if the parameters are different.

[airtonix]

actually I wrongly assumed this was initiated in the directive, however the directive still makes up part of the problem by not allowing an update on same segmentname, different parameters.

[airtonix]

Nvm, Looking at the source code reveals:

https://github.com/artch/angular-route-segment/blob/master/src/route-segment.js#L55

             *                        - `dependencies` is an array of route param names which are forcing the view 
             *                              to recreate when changed;

Which means that :

$routeSegmentProvider
    .segment('page', {
                templateUrl: "page.html",
                dependencies: ['slug', ],
                controller: ["$scope", "$routeParams", function ($scope, $routeParams){
                    $scope.PageUrl = "pages/" + $routeParams.slug + ".html";
                }]
            });

Will cause the segment to update with the routeParam slug changes.

Perhaps the example needs to use this in the example.

[artch]

You can also use watcher property for this purpose:

.segment('segmentName', {
  ...
  watcher: function(SomeService) {
    return SomeService.someValue(); // if this is changed on $digest-ing, then segment will be reloaded
  }
})