-
Notifications
You must be signed in to change notification settings - Fork 64
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
Effectively leverage typed errors by defining precise sealed hierarchy of errors #74
Labels
Comments
/bounty $100 |
💎 $100 bounty • ZIOSteps to solve:
Thank you for contributing to zio/zio-jdbc! Add a bounty • Share on socials
|
/attempt #74 |
💡 @pablf submitted a pull request that claims the bounty. You can visit your org dashboard to reward. |
💡 @pablf submitted a pull request that claims the bounty. You can visit your org dashboard to reward. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ideally, we would have a
sealed trait
that defines every possible error that can result from JDBC, each as a case class that stores relevant context, including any underlyingThrowable
. The sealed trait should be engineered to group related exceptions into a finite number of logical categories. We need confidence that we have done enough research to perform this grouping and that it is necessary and sufficient for all JDBC methods. Finally, we need to update all query methods to return the more precise error type, usingrefineToOrDie
, etc.The text was updated successfully, but these errors were encountered: