Angular ui-router, routing problems with :id. $stateParams empty

Question

in my routes(states) config I have:

state('users', {
            abstract:true,

            templateUrl: '/path/to/template.html',

            access: { isPrivate: 0 },
            resolve: {
           ...a resolve block..



    }).state('users.me',{
            url: '/users/:id/',
            controller: 'userCtrl',
            access: { isPrivate: 0 },
            views:{
                'userView':{
                    templateUrl:'/path/to/template.html'',
                    controller:'userCtrl',

                },
                'view1':{
                    templateUrl:'/path/to/template.html'',
                    controller:'anotherCtrl',

                },
                'view2':{
                    templateUrl:'/path/to/template.html'',
                    controller:'anotherCtrl',

                },
                'view3':{
                    templateUrl:'/path/to/template.html'',
                    controller:'anotherCtrl',

                },
                'view4':{
                    templateUrl:'/path/to/template.html',
                    controller:'anotherCtrl'
                }
            }

In the resolve for this view I have:

 user: function (Restangular, tokenService, $q,$stateParams) {
                    var token = tokenService.getAccessToken();
                    console.log('params',$stateParams) //logs an empty object
                    return Restangular.one('users',($stateParams.id || "me")).get({ header:header });
                }

but for some reason, even if change the url to /users/5/ the resolve functions (that should resolve the correct data for the user) get an empty $stateParams.id and auto resolves to the default 'me'.

What am I missing? I'll be glad for help with this!

Have you tried this without the trailing slash?

peaceman
– peaceman

2013-11-28 13:28:27 +00:00
Commented Nov 28, 2013 at 13:28 — peaceman
– peaceman, Commented Nov 28, 2013 at 13:28
@peaceman yeah, didn't help

alonisser
– alonisser

2013-11-28 13:51:42 +00:00
Commented Nov 28, 2013 at 13:51 — alonisser
– alonisser, Commented Nov 28, 2013 at 13:51

alonisser · Accepted Answer · 2013-11-28 14:27:06Z

5

the problem was the placement of the resolve in the abstract state. moving it one level down works. seems that the abstract state resolve is called only when moveing in or out the abstract state. but moving between /users/4/ and /users/5 doesn't move between states.

this is just my guess. but it works (for now)

UI-router is great but I would really wish the docs were clearer.

answered Nov 28, 2013 at 14:27

alonisser

12.2k21 gold badges89 silver badges144 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Phil Thomas Over a year ago

In the original question the placement of the resolve is unclear. I assumed it was in the nested child.

Nate Abele Over a year ago

Ping @timkindberg on GitHub whenever you'd like to help out with the docs.

Phil Thomas · Accepted Answer · 2013-11-28 14:06:23Z

1

Try replacing your code section:

}).state('users.me',{
        url: '/users/:id/',

with:

}).state('users.me',{
        url: '^/users/:id',

I use this in a ton of places and it works perfectly.

answered Nov 28, 2013 at 14:06

Phil Thomas

1,2371 gold badge12 silver badges33 bronze badges

2 Comments

Phil Thomas Over a year ago

I'm glad you figured it out.

John Spiteri Over a year ago

@PhilThomas this helped me - allowing browser refreshing to happen.

Rick · Accepted Answer · 2014-12-28 17:50:07Z

1

Alternative would be the following

.state('user.update-user',{
  url: '/update-user/:userId',
  templateUrl: '/views/update-user.html'
}

And the links would look something like this

 <a ui-sref='user.update-user({userId: use._id})'><i class="fa fa-pencil-square-o"></i></a>

answered Dec 28, 2014 at 17:50

Rick

13.6k3 gold badges46 silver badges42 bronze badges

Collectives™ on Stack Overflow

Angular ui-router, routing problems with :id. $stateParams empty

3 Answers 3

2 Comments

2 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

2 Comments

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related