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
A PR was sended a long time ago but it doesn't get merged #9465, it doesn't include SEARCH (it is an old WebDav method) but can be as a base to include all the WebDav methods.
What is the motivation / use case for changing the behavior?
Allow to use the SEARCH HTTP method as the other ones, is a "GET with body" without break any standard.
The text was updated successfully, but these errors were encountered:
I'd be really interested in working on this issue, but I'm quite new to open sourcing and to this project codebase, could someone help me get through it? 😄
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
I want to use the SEARCH HTTP method with NestJS but it doesn't have the @Search() decorator as @get(), @post(), etc
Describe the solution you'd like
Create a @Search() decorator for use in the controllers.
Teachability, documentation, adoption, migration strategy
Same use as the actual HTTP methods decorators.
Express and Fastify already supports it
http://expressjs.com/en/4x/api.html#routing-methods
https://www.fastify.io/docs/latest/Reference/Routes/#routes-options
A PR was sended a long time ago but it doesn't get merged #9465, it doesn't include SEARCH (it is an old WebDav method) but can be as a base to include all the WebDav methods.
What is the motivation / use case for changing the behavior?
Allow to use the SEARCH HTTP method as the other ones, is a "GET with body" without break any standard.
The text was updated successfully, but these errors were encountered: