Wrong Routing Dataset - Router\Standard

[brunoaugusto]

Although the current implementation of Standard Router is already addressing the scenario described in the doc-comment of Next\Tools\RoutesGenerator\Annotations::sort() it doesn't consider cases in which the most generic route is also the longest route. E.g:

/management/actors/overview
/management/actors/add

These two routes, in the fictional movies database system example in the doc-comment mentioned above, could be used to describe, respectively, a small overview of all actors registered and a form to add new actors.

Conceptually the longest route here is less specific than the short one, but because they are are sorted in that way, because the sorting is done by the Routes Generator tool, the current implementation of SQLite REGEXP operator using preg_match() will return the first entry as positive for the second URI, because both of them have the immutable part management/actors

[brunoaugusto]

Further tests proved commit c19f715 not only did not solve the issue mentioned here but also prevented Routing Arguments to work properly.

Currently, the only way to avoid this limitation is to code the Action Methods with the longest but more generic routes, after the shorter and more specific ones.

The referred changes will be reverted.