Add RequestContext and logging #176
Open
+570
−33
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 pull request continues the work in #104 and solves the problem in #161. Ping @Adebayo120 and @AgentSlim
We introduce a
RequestContextMotivation and Context
We want to have request specific services that only live in the context of a
RequestHandlerInterface. Ie services that has access to theSession. These cannot live inside the PSR-11 Container.PR #104 added a
ClientLoggerwhich would live next to our existingClientGateway. To avoid adding more and more features inReferenceHandler, I created aRequestContextwhich gives you access to session and request data (like metadata). TheRequestContextwill also build you aClientGateway.How Has This Been Tested?
Tested with unit test and Inspector
Breaking Changes
Yes. I have just deprecated
ClientAwareInterface. I would like to remove it. Should I do it in this PR?Types of changes
Checklist
Additional context