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 your feature request related to a problem? Please describe.
Currently, the GET method in the webhook event handling only supports capturing query parameters, and the POST method only sends the body of the request. This limitation reduces flexibility and functionality when interacting with the API, as it does not allow for the integrated sending or capturing of other important data like headers and both query parameters and body across all requests.
Describe the solution you'd like
I would like all HTTP methods (GET, POST, PUT, DELETE, etc.) to handle the data sent in query parameters, headers, and body in an integrated manner. Specifically, this would involve modifying the route handling functions to capture and send all this data regardless of the HTTP method used. This would allow for greater flexibility in handling requests and responding to webhook events.
Describe alternatives you've considered
Extend the current functionality of each method to optionally capture headers and other data through additional configurations in the route definition.
Additional context
Here is the relevant code that might need changes to implement this enhancement:
Is your feature request related to a problem? Please describe.
Currently, the GET method in the webhook event handling only supports capturing query parameters, and the POST method only sends the body of the request. This limitation reduces flexibility and functionality when interacting with the API, as it does not allow for the integrated sending or capturing of other important data like headers and both query parameters and body across all requests.
Describe the solution you'd like
I would like all HTTP methods (GET, POST, PUT, DELETE, etc.) to handle the data sent in query parameters, headers, and body in an integrated manner. Specifically, this would involve modifying the route handling functions to capture and send all this data regardless of the HTTP method used. This would allow for greater flexibility in handling requests and responding to webhook events.
Describe alternatives you've considered
Extend the current functionality of each method to optionally capture headers and other data through additional configurations in the route definition.
Additional context
Here is the relevant code that might need changes to implement this enhancement:
eventsources/sources/webhook/start.go#L167
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: