Pass action to container.get
#1
Merged
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.
The IoC integration lacks the request context when resolving instances of a controller. This context is very useful for many IoC integrations that manage their lifecycle on a per-request basis.
As an example, if the consumer wants to bind the request IP address in a child container so that it is available in a request scope, then they'll need to do this work just before the controller gets created. For example:
Here, the resolved controller and all of its dependencies will have access to the IP of the current request scope.
The
action
has been added as an optional second argument to theget()
callback so that it's backwards compatible with existing code.