Route precedence

As routesMap is an object and the order of route matching depends solely on Object.keys return value. If I do something like:

const routesMap = { 
  HOME: '/home',
  USER_NEW: '/user/new',
  USER: '/user/:id',
}

There’s absolutely no guarantee that the USER_NEW route has the precedence over the USER route.

It’s possible to use regex in the matching:

const routeMaps = {
  HOME: '/home',
  USER_NEW: '/user/new',
  USER: /user/(((?!new).)*)$/
}

But that would cause the payload to be number indexed instead of named: {0: "123" }

Is this by design? This use case would definitely be benefited by some ordering mechanism in the routes. Either an order parameter or routesMap accepting an array instead of an object would be fine I believe.

Do you see this as a valid use case?

[faceyspacey]

good point. …though if the order is only dependent within the given injection (which is likely the case 90% of the time), then we’re right where we were before.

I probably will do the order feature at a certain point. Other things will also make it important, like URLs that are more dynamic than :param which use regexes.

[GuillaumeCisco]

Sorry to comment this closed issue, but I think something important was pointed out by this discussion. If the implementation of injected routes is made, I think the order will be very very important. But maybe I’m wrong.

The package normalizr transform objects in two nested objects : one entities with an object of {id: object} objects, another with a results list with the id in order. Maybe it will be usable. Just an idea.

Thoughts ?