$stateParam parsing behaviour changed in 0.2.12

[mkulke]

Hello there,

In 0.2.11 the url params test/:id were parsed to numbers in some cases (it did for ui-sref, but not for href or direct links). in 0.2.12 this behaviour changed to being parsed always to string. Is this by purpose?

0.2.12 plnkr
0.2.11 plnkr

Our tests are written like described in the wiki (https://github.com/angular-ui/ui-router/wiki/URL-Routing#stateparams-service):

$stateProvider
    .state('contacts.detail', {
        url: "/contacts/:contactId",
        templateUrl: 'contacts.detail.html',
        controller: function ($stateParams) {
            // If we got here from a url of /contacts/42
            expect($stateParams).toBe({contactId: 42});
        }
    })

and fail w/ 0.2.12 then.

[christopherthielen]

Hi, you're seeing

default to parameter string coersion. (13a468a, closes #1414)

https://github.com/angular-ui/ui-router/blob/master/CHANGELOG.md

If you want int parameters, now you can declare it and always get ints (not sometimes-ints-sometimes-strings)

$stateProvider
    .state('contacts.detail', {
        url: "/contacts/{contactId:int}",
        templateUrl: 'contacts.detail.html',
        controller: function ($stateParams) {
            // If we got here from a url of /contacts/42
            expect($stateParams).toBe({contactId: 42});
        }
    })

Please close if this answers your question.

[mkulke]

Yes. thanks for the quick clarification, i updated the wiki accordingly, i hope that's fine.

[christopherthielen]

i hope that's fine.

yes, thanks!