Laravel. Be careful when using solo dynamic segments on Routes

First and foremost I’d like to illustrate what I call dynamic segments:

Dynamic Segment

Route’s dynamic segment receive information provided by users and they are tipically used to retrive stored data. In the image above both id and slug are used to query the database.

Working with routes and dynamic segments is something trivial and unlikely to give you any problem but there’s one situation which might make you run into some trouble.

Let’s take a look at the code below:

A typical Laravel's route set...

This is nothing more than a bunch of grouped routes. The $config array contains - among other things - the prefix for all the group’s routes.

The URL for the route configured on line 11 will be something like http://domain.com/feature. On line 12 there’s another route which URL will be http://domain.com/feature/< anything here >

Got the issue?

This < anything here > could be an integer (an ID for instance), could be a slug as declared in the route (my-wonderful-post-dat-will-change-your-life-foreva) OR it could be simply novo (new, in english…).

Let me draw it for you:

. http://domain.com/feature/187
. http://domain.com/feature/my-wonderful-post-dat-will-change-your-life-foreva
. http://domain.com/feature/new

Well, according to the script above route /new will never be reached, because “novo” might as well be a slug and then the script execution will stop on line 12, never getting to line 13, which is the original intent.

The easiest solution is to move the code in the line 12 to the end of route’s set. So, when all the more specific routes are checked and retuned false, then the request will certainly reach slug’s route.

The solution