feat: allow before_request and after_request handlers to accept a parent argument #3748
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.
…to wrap or override the handler from an enclosing scope.
At present, this is a proposal / discussion piece rather than a contribution submitted as ready-to-merge.
Description
Presently, hooks at an inner layer replace those at outer layers. In many use cases, this is unsuitable: If the router handling all
/tenants/{tenant:uuid}
requests performs a lookup and authentication, then a router mounted under it will still want that same authentication even if it adds additional common code as well.This PR proposes a change to allow child handlers to wrap parent handlers. Where previously one might write:
...we can instead write:
...and let litestar do the work of populating
parent
as/when appropriate.