Nest 5.0.0-rc.2 Swagger example not correct generate parameters

I’m submitting a…

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

Current behavior

Swagger example not correct generate parameters

Expected behavior

parameters should generate correct.

Minimal reproduction of the problem with instructions

use example codes: https://github.com/nestjs/nest/tree/master/sample/11-swagger

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

Environment

Nest version: 5.0.0-rc.2

 
```
{
    "@nestjs/microservices": "^5.0.0-rc.2",
    "@nestjs/common": "^5.0.0-rc.2",
    "@nestjs/core": "^5.0.0-rc.2",
    "@nestjs/passport": "^1.0.6",
    "@nestjs/swagger": "^1.2.2",
    "@nestjs/testing": "^5.0.0-rc.2",
    "@nestjs/typeorm": "^2.0.0",
    "@nestjs/websockets": "^5.0.0-rc.2",
    "class-transformer": "^0.1.7",
    "class-validator": "^0.7.2",
    "reflect-metadata": "^0.1.12",
    "rxjs": "^6.0.0",
    "rxjs-compat": "^6.0.0",
    "typescript": "^2.8.0"
  }
```

For Tooling issues:
- Node version: XX  
- Platform:  

Others:

[edevil]

@kamilmysliwiec I also have to specify ApiImplicitParam otherwise the params do not show up in the UI:

  @Get(':id/:id2')
  @ApiImplicitParam({ name: 'id2' })
  @ApiImplicitParam({ name: 'id' })
  findOne(@Param('id') id, @Param('id2') id2) {
    return `This action returns a #${id} cat #${id2}`;
  }

Is this expected? In addition, I installed nest (CLI) from scratch today and got these versions:

[System Information]
OS Version     : macOS High Sierra
NodeJS Version : v8.12.0
NPM Version    : 6.4.1
[Nest Information]
swagger version : 2.5.1
common version  : 5.1.0
core version    : 5.1.0

Isn’t 5.4.0 the latest Nest version?

[Thatkookooguy]

@kamilmysliwiec @vellengs Not sure why this is happening, but from my investigation, you can fix this by adding a type of string to that function argument. for example:

This will NOT generate the swagger parameter:

  @Get('/raw/:username')
  getUser(@Param('username') username): string {
    return 'given user: ' + username;
  }

But this WILL

  @Get('/raw/:username')
  getUser(@Param('username') username: string): string {
    return 'given user: ' + username;
  }

the only difference is in this part: @Param('username') username: string where I set the username parameter to be a string.

Since most of the examples here didn’t include types for the function arguments, I thought I might share this because this might solve the problem in the meanwhile for people.