Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
The generated OpenAPI document will not include QUERY endpoints.
Describe the solution you'd like
We now have a spec for the HTTP QUERY method. There is a PR to support this in core Nest. Once that lands I'd love to see support for QUERY in the OpenAPI package.
It appears that the OpenAPI standard itself supports QUERY. It's just that the Nest (and OpenAPI implementation) don't support it yet.
I understand that this may have to wait for the above core Nest PR to land. But I wanted to start an issue to track it.
Teachability, documentation, adoption, migration strategy
No response
What is the motivation / use case for changing the behavior?
I want to start exposing QUERY endpoints in my Nest-based REST API. This would be much nicer than GET endpoints with a bunch of optional query parameters.
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
The generated OpenAPI document will not include QUERY endpoints.
Describe the solution you'd like
We now have a spec for the HTTP QUERY method. There is a PR to support this in core Nest. Once that lands I'd love to see support for QUERY in the OpenAPI package.
It appears that the OpenAPI standard itself supports QUERY. It's just that the Nest (and OpenAPI implementation) don't support it yet.
I understand that this may have to wait for the above core Nest PR to land. But I wanted to start an issue to track it.
Teachability, documentation, adoption, migration strategy
No response
What is the motivation / use case for changing the behavior?
I want to start exposing QUERY endpoints in my Nest-based REST API. This would be much nicer than GET endpoints with a bunch of optional query parameters.