Allow to change body parameter name derived from @Body()

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

I wrote a controller like this:

  @Post('/')
  @ApiImplicitBody({ name: 'body', type: MemberCreatePayloadApi })
  public async create(@Body() payload: MemberCreatePayloadApi): Promise<Member> {
  }

SwaggerModule produces the below api from my controller.

      "post": {
        "parameters": [
          {
            "name": "body",
            "required": true,
            "in": "body",
            "isArray": false,
            "schema": {
              "$ref": "#/definitions/MemberCreatePayloadApi"
            }
          },
          {
            "name": "MemberCreatePayloadApi",
            "required": true,
            "in": "body",
            "schema": {
              "$ref": "#/definitions/MemberCreatePayloadApi"
            }
          },
        ],

Expected behavior

@Body() makes a parameter named by argument type. But I want to change parameter name as I like.

# Expected output
      "post": {
        "parameters": [
          {
            "name": "body",
            "required": true,
            "in": "body",
            "isArray": false,
            "schema": {
              "$ref": "#/definitions/MemberCreatePayloadApi"
            }
          },
        ],

I try to modify explorer, the below code is expected to me but it may lose backward compatibility.

https://github.com/nestjs/swagger/blob/master/lib/explorers/api-parameters.explorer.ts#L90

- val => val.in === DEFAULT_PARAM_TOKEN || (val.name && val.in === 'body')
+ val => val.in === DEFAULT_PARAM_TOKEN || (val.in === 'body')

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

A client library swagger-js users should name request body parameter body.

Environment

@nestjs/core: 5.5.0
@nestjs/swagger: 2.5.1

Thanks.

[akkunchoi]

@kamilmysliwiec Hi, I fixed this issue as above. Can I get your opinion?

[kamilmysliwiec]

Added in the next version (to install run npm i @nestjs/swagger@next). Note: remember to update @nestjs/common, @nestjs/core and typescript as well to ensure that you’re using the latest versions.

Steps to migrate: https://github.com/nestjs/swagger/pull/355#issuecomment-547925879