state.go not passing data to $stateParams

[nikilster]

I'm currently passing in data as part of the second argument to state.go and when I check in the state params of the destination controller, $stateParams is empty.

Been trying to figure this out for an hour - I think I'm doing everything correctly?

$state.go("send-to", { "test": 123});

and when it transitions to the "send-to" controller I see

console.log($stateParams); // -> Empty {}

[roryf]

What does your "send-to" state definition look like?

[nikilster]

app.js

 $stateProvider

    <omitted>

    .state('send-to', {
      url: '/send-to',
      templateUrl: 'templates/send-to.html',
      controller: 'SendToCtrl'
    })

controllers.js

.controller('SendToCtrl', function($scope, $stateParams, $state) {

    console.log($stateParams);

[timkindberg]

you need to specify the param in the url url: '/send-to/:test'

[psi-4ward]

Hi, having a similar issue but i wont define a url for my state! Is there no way to populate $stateParams without using an url?

[timkindberg]

params property on a state config. Look in docs.

[psi-4ward]

found it! but through studying the source not in the docs, ill prepare a pull

[timkindberg]

http://angular-ui.github.io/ui-router/site/#/api/ui.router.state.$stateProvider#state, scroll down to params property. Not exactly easy to find, but technically exactly where it should be.

[psi-4ward]

Exactly! i studied the wiki pages, we should add a hint for that.

[timkindberg]

The ngdoc site is new, the wiki should really just be used for an intro guide.

[psi-4ward]

Than we sould really add the deprecated hint from Quick-Reference to the [Wiki-Startpage](to https://github.com/angular-ui/ui-router/wiki)

[timkindberg]

Well the start page is still fine, it gets new users going quickly, but the API reference is now deprecated. We may eventually move the In-Depth Guide over to the ngdoc site as well, but for now its all fine.

[psi-4ward]

Perhaps you could update like: https://github.com/psi-4ward/ui-router/wiki#params
and https://github.com/psi-4ward/ui-router/wiki/URL-Routing#custom-parameters

However im really not happy with the strict url or params solutions and only String.
Ive ovten the situation where i would "inject" a ready to use Object rather than have to resolve it again using its ID.

[timkindberg]

Yeah unfortunately that's all we support right now. We'd like to work towards more object types supported as params in the future.

[bramski]

This is a most annoying shortcoming. There does seem to be a workaround to have both a url and a params object:

.state 'schedules',
        url: '/schedules'
        views: _({}).extend schedule_views,
          'content@':
            templateUrl: 'views/schedules/schedules.html'
            controller: 'SchedulesCtrl'
.state 'schedules.manage',
  params: ['pinCode']