Route paths must be sorted after definition and before adding them to express.

[guimello]

Problem

Routes must follow a precedence definition when adding them to express.

app.get('things/:id', func);
app.get('things/dance', func);

The second api will never match because the dynamic id key will match dance. So in order to solve this, the routes must be defined as such:

app.get('things/dance', func);
app.get('things/:id', func);

Proposal

Maybe we should automatically sort the routes by their path definition, giving precedence to not dynamic path keys.

Pros

• avoid user mistake when defining routes

Cons

• doing this automatically could be an issue if later on the road we allowed Route#path to be a function instead of string.

[fsmaia]

Amazing idea 🚀
I think we could create our own Request and Response interfaces too (even if they just extend express), so users wouldn't be aware of express complexity and interfaces :)