Using `type: () => TYPE` in `@ApiOperation` decorator results in invalid swagger generation

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

The documentation states to change type: TYPE to type: () => TYPE to avoid cyclic dependency errors. However, this only works in @ApiProperty() and @ApiPropertyOptional() decorators. It does NOT work in @ApiOperation() and related decorators.

Expected behavior

It should work for @ApiOperation() decorators.

Minimal reproduction of the problem with instructions

Check out the change in the test-case I made in my fork that exposes this error when you run npm run test:e2e. The generated openapi schema is broken.

https://github.com/nestjs/swagger/compare/next...loban:loban-another-schema-error

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

This is necessary for the library to be usable.

Environment

Nest version: 4.0.0-next.3
 
For Tooling issues:
- Node version: 12.12.0
- Platform:  Mac

[loban]

@nartc Well, I instead just made a fix so that @ApiOperation can now properly handle lazy-evaluated-type-functions. PR at #375 .

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.