Collisions in rest params

[lushchick]

I have rest params with the same /path/:name in different routes. When I specify regex for one of them - it is used then for the other param as well. It might be because of some collisions in hash key names in pipeline-router, or the order of params in their storage container.

[panthershark]

This is due to differences in pipeline router and mixdown router semantics. This bug has been in the backlog in my head and it might take some changes to both repos.

The short answer reason is that pipeline-router caches the params at the factory level, not the instance level.

The near term solution is to give routes that use different regex for params different names. Another near term tweak would be to have mixdown router detect and emit the warning on app startup. It would not fix the issue, but would make the library more proactive.

[lushchick]

Thanks for the clarification, i think i will use different names for now.