Param matchers greedy match defined routes

const routes = [
  { name: 'home', path: '/' },
  { name: 'home.moo', path: 'moo' },

  { name: 'eviltroll', path: '/:catch' } 
]

// Expect to match "home.moo"
router.matchPath('/moo')
// -> { name: 'eviltroll', params: { catch: 'moo' } ...

😦

I’m probably doing something wrong here, because this seems like quite an obvious use-case, defining one set of handlers for matching routes, and letting mis-hits continue through to the rest of the defined routes. What I didn’t expect was for the ‘param’ operator (eviltroll) to be greedy and match the route defined by the “home.moo” handler.

Is this expected behaviour? And if so, can the intended match above be reached some other way?

Thanks!

[cayuu]

Thanks Thomas, understood. Will design for this consideration. #closing

[troch]

To clarify: when two path definitions like /moo and /:param are siblings (they are children of the same parent node), /moo is tried before /:param.

The reason for not returning all matches and then picking the “best” one (i.e. the most specific one - with less params) is a design decision for increased performance and scalability: especially in the scenario of server-side rendering. That kind of match strategy is common server-side: the first match is the match.