is a "catchAll" route impossible by design?

[ingoradatz]

The catchAll route "(*path)": "catchAll" used in the ampersand demo webapp must be the last route in the hash. Otherwise every route defined after is impossible to reach.

{
  "index.html": "home",
  "collections": "collectionDemo",
  "info": "info",
  "person/add": "personAdd",
  "person/:id": "personView",
  "person/:id/edit": "personEdit",
  "(*path)": "catchAll"
}

The Problem is that the object key sorting is not static. I have handled the routes as JSON before using it to extend the router and they got sorted alphabetically. In result the catchAll-Route enters the first place.

{
  "(*path)": "catchAll",
  "collections": "collectionDemo",
  "index.html": "home",
  "info": "info",
  "person/:id": "personView",
  "person/:id/edit": "personEdit",
  "person/add": "personAdd"
}

Should we switch to an array of routes or oversee i something that solves the problem an other way?

[kamilogorek]

@llabball that's correct that order matters here and if you'll resort your routes, they simply won't work. Please let me know if you'd like to discuss this issue in depth, so I'll reopen this ticket then.