API Versioning: Multiple versions for controller not displayed properly in Swagger

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

When enabling API Versioning in Nest and adding multiple versions to a controller, the correspondig Swagger Docu only shows routes for the first entry of the versions array (https://github.com/jalorenz94/api-versioning).

import { Controller, Get } from '@nestjs/common';
import { AppService } from './app.service';

@Controller({
  version: ['1', '2'],
})
export class AppController {
  constructor(private readonly appService: AppService) {}

  @Get()
  getHello(): string {
    return this.appService.getHello();
  }
}

Expected behavior

The swagger docu shows the following endpoints: /v1 and /v2.

Minimal reproduction of the problem with instructions

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

Environment

Nest version: 8.0.0
Nest Swagger version: 5.0.9

 
For Tooling issues:
- Node version: 16  
- Platform:  Linux 

Others:

[mahmoudmaamounz]

Hi @kamilmysliwiec I am experiencing a related issue and happy to address this in PR but wanted to make sure I am doing it correct.

I am adding @Version('1') to a route and the swagger documentation doesn’t show the version at all. Is this a bug or that wasn’t implemented? How do I get the version to show should I hardcode it in the route? Thanks!

This is how I am implementing it now

  @Version('1')
  @Post()
  async test(@Body() body: Payment): Promise<string> {

[kamilmysliwiec]

Would you like to create a PR to address this issue?