4.x - Add Possibility For Custom RequestHandler Invocation Strategies #2774
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.
This effectively closes #2772 and #2773
Added a new interface for invocation strategies that can handle request handlers:
The current
RequestHandler
strategy now implements that interface which enables to check within theRoute::run()
method that the user set strategy can handle request handlers. In the event that it doesn't, a newRequestHandler
strategy is instantiated.Also added feature to the existing
RequestHandler
strategy (requested in #2772/#2773) to append route arguments as attributes to the incoming request object. By default it is set tofalse
. If you want to enable this feature:To enable the feature for all the routes:
To enable the feature on a per route basis: