dynamic routes that match static routes

[ryanflorence]

<Route name="contact" path="/contact/:id" handler={Contact}/>
<Route name="new"     path="/contact/new" handler={NewContact}/>

In this scenario transitioning to "new" will incorrectly match "contact" first and render. Reverse them and it'll work as expected like below:

<Route name="new"     path="/contact/new" handler={NewContact}/>
<Route name="contact" path="/contact/:id" handler={Contact}/>

[mjackson]

As we discussed on IM, I'd say this is a bug in the JSX. We traverse the routes tree depth-first when looking for a route that matches. This makes it easy for people to follow when they're debugging stuff.

Ideally we could have some sort of "unreachable route" warning in this scenario to stop people from shooting themselves in the foot, but I'd be ok closing this for now.

[mjackson]

Closing this for now since we've got a few specs going..