Capture the previous exception in generic ServiceException #143
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Status
READY
Description
Currently the
ServiceException::generic()is thrown in a couple of places where an unknown exception occurred while sending the payload, and it discards the exception that was originally thrown, losing any context. Seehoneybadger-php/src/HoneybadgerClient.php
Lines 45 to 47 in 95ea3d9
Additionally, this PR adds an
unexpectedResponseCode()exception factory, to be used instead ofgenericwhen the response code is unexpected, since we do know what the problem is.