Integer/Float URL Parameters, Maintain Type

[rynz]

Consider a state which has url: '/example/{exampleId:[0-9]}' and that we navigate our application to /example/5.

Inspecting $stateParams the result is {exampleId: "0"} and thus exampleId is a string. If we later use this result to perform ajax queries or other operations we may run into a few issues and have to convert the string at the client or server side.

Perhaps $stateParams could check if the value is an integer/float and store it as such, else store as string? Or have a an additional option within the url:{} param to determine if it is to be stored as a string or not?

[ksperling]

The intention is to support typed parameters, something along the lines of

$urlMatcherFactory.registerType('int', {
  pattern: /[0-9]+/,
  encode: function (val) { return String(val) },
  decode: function (s) { return Number(s) },
})
...
$stateProvider.state({
  'url': '/foo/{exampleId:int}',
})

[rynz]

Okay so it is planned, great thank you @ksperling

[chiefy]

👍 Just ran into this getting into ui-router. Bad assumption on my part (that a match on [0-9] would result in a Number).

[nateabele]

This has been implemented in a branch and will be coming in the next release.

[chiefy]

@nateabele Awesome news, thanks!

[christopherthielen]

This feature is now functional in 0.2.12

[xDisfigure]

FYI - Using Int params type with "offlimit number"
Becareful using int as parameter type with than kind of number 116410000002753064.

If you pass 116410000002753064 into Number/String like uirouter int params does.

Number(116410000002753064) // output: 116410000002753060
Number(116410000002753064123123912) // output: 116410000002753060000000000

Same using String()

I had to use pattern ([0-9]+) instead of int on my param to make it work as expected.