How to specify the error response types for swagger

[loucass003]

Using the nestjs swagger api, I used to set the response errors and code with the different decorators like so

  @Header('Cache-Control', 'no-cache')
  @ApiOperation({
    description: 'Build a specific configuration of the firmware',
  })
  @ApiOkResponse({ type: BuildResponseDTO })
  @ApiBadRequestResponse({ type: VersionNotFoundError })
  buildFirmware(@Body() body: CreateBuildFirmwareDTO) {
    return this.firmwareService.buildFirmware(body);
  }

How can I specify those possible responses with nestia?

[loucass003]

it looks like a good way to support this could be to check the
@throws and if the type is an http exception specifying the response code and the payload

Something like this perhaps?

  /**
   * @throws {import("./errors/version-not-found.error").VersionNotFoundExeption}
   */
   @TypedRoute.Post("/build")
  buildFirmware(@Body() body: CreateBuildFirmwareDTO) {
    return this.firmwareService.buildFirmware(body);
  }

export const VersionNotFoundError = 'Version not found';
export class VersionNotFoundExeption extends HttpException {
  constructor() {
    super(VersionNotFoundError, HttpStatus.BAD_REQUEST);
  }
}

[samchon]

Will support new decorator function @TypedException<T>().

But as I'm working another thing (typia.protobuf), this feature would be implemented later.

[loucass003]

Is there at least a way to use both legacy decorators and nestia to generate a swagger document?

that would allow us to keep using nestia while waiting for the exceptions to be implemented. Not having this feature would mean that we would have to stop using nestia in our project

[samchon]

Good idea, I will.

Not possible to adapt @ApiBadRequestResponse like decorators in nestia.

Instead, I'll provide you @TypedException<T>(), and it may not require lots of modifications.

The next version will be published at this week.

[samchon]

#548

Upgrade to v1.6.4, then what you want would be prepared.