feat(event-handler): implement mechanism to manipulate response in middleware #4439
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This commit introduces a mechanism for middleware to manipulate HTTP responses sent by the handler. This is required for middleware such as CORS.
Changes
BaseRouter.ts
HandlerOptions
now exposes ares
field. This is a Web APIResponse
object that represents the response that will be sent. This allows middleware that runs after the handler has been executed to manipulate the response before it is finally sentres
field and adds the response thereRequestOptions
toRequestContext
because it now deals with responses as well as requestsConverters.ts
HandlerResponse
for a Web APIResponse
object.Tests:
handlerResultToResponse
fucntioncomposeMiddleware
Issue number: closes #4393
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.