Route priority

[macalinao]

GitHub has its /settings route with a higher priority than the /:username route. Is this possible with ui-router? I wasn't able to find any documentation on it. Thanks.

[christopherthielen]

I believe routes are matched in the order they are defined. However, exact matches take precedence over parameterized matches.

[macalinao]

Is there a way to supply a number for priority? I can't specify the order
of the files beforehand as I am using an injection script.
On Aug 26, 2014 6:59 PM, "Chris Thielen" notifications@github.com wrote:

I believe routes are matched in the order they are defined. However, exact
matches take precedence over parameterized matches.

—
Reply to this email directly or view it on GitHub
#1277 (comment)
.

[christopherthielen]

no, sorry, not currently possible.

[orrgal1]

it doesn't look like exact matches have a higher priority...

[christopherthielen]

@orrgal1 I could have been wrong about that, sorry. I'm not sure if we have specified that behavior

[orrgal1]

no worries thanks, just wanted to make sure

On Tue, Jun 16, 2015 at 4:30 AM, Chris Thielen notifications@github.com
wrote:

@orrgal1 https://github.com/orrgal1 I could have been wrong about that,
sorry. I'm not sure if we have specified that behavior

—
Reply to this email directly or view it on GitHub
#1277 (comment)
.

[plong0]

Found a solution here: http://stackoverflow.com/questions/26389177/angularjs-ui-router-incorrectly-interpreting-url-path-as-paremeter-in-urlroute

Explicitly defining the higher priority route in the $urlRouterProvider works.

ex:

$stateProvider.state('foo.bar', {url: '/foo/:bar'});
$stateProvider.state('foo.baz', {url: '/foo/baz'});
$urlRouterProvider.when( '/foo/baz', function($state){ $state.go('foo.baz'); } );

[aeharding]

I also have this problem. It would be nice if routes declared earlier had priority, or there was some sort of smart detection to see which route is more general.

Is this fixed in ui-router 2?

Just to show what routes were giving me trouble:

/contact/new
/contact/:id

In this case, /contact/:id is always chosen by ui-router. Switching it around gets the desired functionality... But only sometimes. ;)

[christopherthielen]

@aeharding what version of ui-router are you on? I think we merged in a PR that tries to prioritize urls based on the length of the prefix (params don't count as prefix)

b5c57c8

[pietro909]

Hi, I ran into the same issue and this is what I found so far:

• routes are matched in the order they are registered
• there is no guarantee about the order we are providing, as children states will be queued until parent state is registered
• as of today the only solution 100% working is the one posted by @plong0 http://stackoverflow.com/questions/26389177/angularjs-ui-router-incorrectly-interpreting-url-path-as-paremeter-in-urlroute but it worries me about performances issues.

Is there any news about it?
thanks

[nateabele]

We have a naïve sorting implementation that is currently broken in 1.0alpha0 but is being patched in alpha1. We plan to expose an API for managing sort order at some point down the road in 1.0.

[aeharding]

@christopherthielen I tried upgrading to that release, but unfortunately, it did not fix the problem. I ended up switching the order of the state declaration, but I still think /contact/new being declared before /contact/:id should ideally catch the route.

Good to hear that v1 might fix this. 👍

[christopherthielen]

See #2502

[rkingon]

If you're using a numerical id vs a string slug then you can use regex on the id param like so: url: "/{id:[0-9]+}". It will only match numerical id's and allow new to route correctly.