Refresh ui-router view when state parameters change?

I would do something like this:

.controller("PageCtrl", function($scope, $state) { $scope.$on("$stateChangeSuccess", function updatePage() { $scope.page = $state.params.slug; }); }); 

I'd be curious if you find a better way - there may be some way to just watch the value of the state slug, but this is clean and clearly articulates what it is that you're watching for.

I am really not fully sure, if I do not miss something here - but, based on the snippets shown in your question:

• PageCtrl is related to state "page.view" and will be run as many times as "page.view" state is triggered
• "page.view" state has declared param slug - url: "/pages/:slug",, which will trigger state change - whenever it is changed
• If the above is true (if I do not oversee something) we can use stateConfig setting - resolve
• there is no need to use $state.params. We can use $stateParams (more UI-Router way I'd personally say)

Well if all that is correct, as shown in this working plunker, we can do it like this

resolver:

var slugResolver = ['$stateParams', '$http' , function resolveSlug($stateParams, $http){ return $http .get("slugs.json") .then(function(response){ var index = $stateParams.slug; return response.data[index]; }); }]; 

Adjusted state def:

.state("page.view", { url: "/pages/:slug", views: { "": { controller: "PageCtrl", templateUrl: "page-view.html", resolve: { slug : slugResolver }, }, }, }) 

And the PageCtrl:

.controller('PageCtrl', function($scope,slug) { $scope.slug = slug; }) 

Check it all in action here

I had this problem in ui-router 0.2.14. After upgrading to 0.2.18 a parameter change does fire the expected $stateChange* events.