Disable deprecation warnings when running in production envs #2375
+25
−2
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.
Closes #2373
Enable error reporting for any kind of error in dev and test envs, but disable reporting of deprecation warnings in production.
This is needed because the
ProblemDetailsMiddleware
wraps the whole execution in an error handler which converts any reported error into anErrorException
. See https://github.com/mezzio/mezzio-problem-details/blob/68a17a0/src/ProblemDetailsMiddleware.php#L101-L118It is good to know about deprecation warnings when in dev, as those need to be eventually fixed, but in production, they should not cause the whole request to fail.
Todo