You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there an existing issue that is already proposing this?
I have searched the existing issues
Is your feature request related to a problem? Please describe it
@ApiParam is not supported in controllers, I don't know if there's any specific reason why it doesn't. But in the use case that I have, it makes sense to be able to use it directly in the controller.
In the example below, I will have to define @ApiParam('it_projeto') in each method, even if it is a param in the controller route.
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
@ApiParam is not supported in controllers, I don't know if there's any specific reason why it doesn't. But in the use case that I have, it makes sense to be able to use it directly in the controller.
In the example below, I will have to define @ApiParam('it_projeto') in each method, even if it is a param in the controller route.
Describe the solution you'd like
I believe that support for class and method would already solve this problem. I don't particularly see any downsides.
Teachability, documentation, adoption, migration strategy
On the page https://docs.nestjs.com/openapi/decorators I believe the only change for the user would be to add "Method/Controller" in the @ApiParam info.
What is the motivation / use case for changing the behavior?
Decrease decorator usage for expected parameters in the controller route.
The text was updated successfully, but these errors were encountered: