Problem when specifying multiple invalid routes

[ameyp]

This is with regards to the commit 7c4c65e.

It works well enough with one invalid route (aka a route missing a :param) but if the user specifies multiple invalid routes, the current one in the routes object is replaced by the new one. This is because utils.getRouteType returns null for both, and so they match. Hence, utils.getRoute returns the current invalid route, which is assigned to currentRoute, and hence replaced by the new invalid route.

Instead of trying to fix this, I believe it would be better to just disallow users from adding invalid routes with an assert. Thoughts?

[jsantell]

👍 I think throwing an error when using invalid routes is a simple solution for this, and can provide useful debugging information