Confusing params when using regexp route patterns

[lo1tuma]

If you are using a regexp route pattern, the match result gets merged into params which is very confusing in addition with query parameters.

Given the route pattern: /^(.*)$/i
The controller action would look like this:

// ...
action: function (params, callback) {
    var matchedRegexpPatternValue = params[0],
        otherQueryParam = params.otherQueryParams;
    // ...
}
// ...

You can see the confusing part is that an array gets merged into an object.

[bigethan]

the regex stuff doesn't play nicely with normal use cases, but it is necessary. My thought for another option would be to add the array to the params as regexMatches and access to that instead of bundling them all into the object.