This repository has been archived by the owner on Jan 29, 2020. It is now read-only.
Eliminate deprecation notices due to request/response decorator usage #393
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 patch does the following:
TemplatedErrorHandler
andWhoopsErrorHandler
to no longer use Stratigility request/response decorator-specific methods. Instead, they now pull values via theoriginal*
request attributes, using default values.Application::run()
method to set theoriginalResponse
request attribute; this allows the above changes to be used with Stratigility versions prior to 1.3 (which is the first release in which that attribute was introduced).Other than the error handling deprecations, this now allows Expressive to run without deprecation notices.