You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All of Jedis exceptions are extended from RuntimeException.
While the majority of Jedis exceptions are by definition, checked exceptions.
This behaviour is misleading and leading to a developer bugs, not handling those exceptions (or maybe just not at the right time).
For example: JedisConnectionException is a RuntimeException while a connection error is an expect scenario (not a good one tho 😅).
So as a developer who uses Jedis, when I execute a command I have to go into the implementation to know which errors I need to handle because my implementation may differ between different exceptions.
Is there a specific reason which justify this kind of implementation?
The text was updated successfully, but these errors were encountered:
All of
Jedis
exceptions are extended fromRuntimeException
.While the majority of
Jedis
exceptions are by definition, checked exceptions.This behaviour is misleading and leading to a developer bugs, not handling those exceptions (or maybe just not at the right time).
For example:
JedisConnectionException
is aRuntimeException
while a connection error is an expect scenario (not a good one tho 😅).So as a developer who uses
Jedis
, when I execute a command I have to go into the implementation to know which errors I need to handle because my implementation may differ between different exceptions.Is there a specific reason which justify this kind of implementation?
The text was updated successfully, but these errors were encountered: