-
Notifications
You must be signed in to change notification settings - Fork 616
Make EncoderException a RuntimeException #1180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #1180 +/- ##
=============================================
+ Coverage 54.59% 95.65% +41.06%
+ Complexity 6360 62 -6298
=============================================
Files 697 3 -694
Lines 33366 184 -33182
Branches 4525 28 -4497
=============================================
- Hits 18215 176 -18039
+ Misses 13692 5 -13687
+ Partials 1459 3 -1456
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you mind explaining the motivation for this change in the PR description and the final commit message?
LGTM otherwise
An error encoding a message is more likely to be unrecoverable than the other way around. Making EncoderException unchecked would reflect this case, instead of forcing teams to use the catch-log-rethrow pattern.
For reference, GSON does something similar
https://www.javadoc.io/doc/com.google.code.gson/gson/latest/com.google.gson/com/google/gson/JsonParseException.html