question: conflict in routes names

[ElegantSoft]

I have the same issue here #213
it solved by regex match ids but I have mongodb _id and this solution will not be helpful and ideas ?

[laurentsmohr]

could you please describe what exactly your problem is? How does it differ with mongodb?
How do your conflicting endpoints look atm?

[ElegantSoft]

My problem is when I GET items/all it go to items/:id
in the mentioned issue it solved by using regex @get('items/:itemId([0-9]+)')
but I am using mongodb and ids is not just numbers it is complex of strings and numbers

[laurentsmohr]

ah, I am actually stuck at some similar problem.
I have two routes @Get('/users/:id') & @Get('/users/:name'). Where my usernames are in the format (anything)-(fourdigits) (e.g.: firstnameLastname-1234)
@Get('/users/:id([0-9]+)') works for the id, which is numerical.
But @Get('/users/:name(.+-[0-9]{4})') does not work, although the regex pattern is correct.

[laurentsmohr]

@NoNameProvided shamelessly asking you for help here

[p493z3r0]

I have a similar issue. Im trying to have an action for a specific user, so my routes look like that:

/api/user/:id
/api/user/:id/action

But i get an "cannot set header twice" error. Is there a known workaround?

[NoNameProvided]

For future readers: a feature landed which prevents this behavior. Now routing-controllers will stop after processing the first matching route.