[Feature Request] Support url parameters without router positions

I’m submitting a…

[ ] Regression 
[ ] Bug report
[x] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

It’s only possible to use parameters if they’re route parameters.

For example, to access name and age, a route must be set up as:

:name/:age

Expected behavior

It should be possible to use url parameters as well:

E.g. http://localhost:3000/cats?name=gary&age=1.57

Minimal reproduction of the problem with instructions

@Get('cats')
async getByNameAndAge(@Param('name') name: string, @Param('age'): number): Promise<object> {
   return Promise.resolve({"name": name, "age": age, "success": true})
}

What is the motivation / use case for changing the behavior?

Url parameters being parsed in any order is better for long lists of parameters and the potential for optional parameters compared to positional route parameters.

Environment

Nest version: 4.6.6

 

[kamilmysliwiec]

I’ll provide an example in the docs.

[chanlito]

@natejgardner you can use @Query('name') or @Query('age') as well.