[Problem] Order of evaluation of routes is the other way round about nest-router HOT 2 CLOSED

@shekohex Thank you very much! Your #43 (comment) really helped me.

Due to the fact that I was having the same problem that @hzburki described, I could easily solve the problem using a regex. In my case, I'm using UUIDs v4. So, the final RegExp for me was:

@Get(':id([0-9a-f]{8}-[0-9a-f]{4}-[4][0-9a-f]{3}-[0-9a-f]{4}-[0-9a-f]{12}$)')

Here's the stack overflow thread to apply to other UUID versions:
https://stackoverflow.com/questions/136505/searching-for-uuids-in-text-with-regex

from nest-router.

I guess that issue related to #43 (see my comment here #43 (comment))

I'm not sure we could go around this, nest-router does not intercept the route definition, it's just a module that collects all the modules/controller and make them in a pyramid like structure.

Also, someone asked a similar question about a similar case and I responded to him here #43 (comment)

from nest-router.