feat: Include exception type in StatusReply toString when not text #31963
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
johanandren
deleted the
wip-include-exception-type-in-statusreply-to-string
branch
patriknw
reviewed
Jun 7, 2023
| case ScalaFailure(ex) => s"Error(${ex.getMessage})" | ||
| case ScalaSuccess(t) => s"Success($t)" | ||
| case ScalaFailure(ex: ErrorMessage) => s"Error(${ex.getMessage})" | ||
| case ScalaFailure(ex) => s"Error(${ex.getClass.getName}: ${ex.getMessage})" |
There was a problem hiding this comment.
doesn't matter, but an alternative could have been ex.toString, which by default does pretty much the same thing but also handles the case of null message for NPE
johanandren
added a commit
that referenced
this pull request
Jun 7, 2023
patriknw
pushed a commit
that referenced
this pull request
Jun 7, 2023
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.
Helps making test assertions easier to understand when using custom exception and they do not match as expected, this is what you can get currently:
java.lang.AssertionError: expected Error(text text text), found Error(text text text)